Merge lp:~mmcm/akiban-server/sql-product-map-depth into lp:~akiban-technologies/akiban-server/trunk
Proposed by
Mike McMahon
Status: | Merged |
---|---|
Approved by: | Nathan Williams |
Approved revision: | 2709 |
Merged at revision: | 2716 |
Proposed branch: | lp:~mmcm/akiban-server/sql-product-map-depth |
Merge into: | lp:~akiban-technologies/akiban-server/trunk |
Diff against target: |
310 lines (+214/-3) 14 files modified
src/main/java/com/akiban/sql/optimizer/rule/OperatorAssembler.java (+7/-3) src/test/java/com/akiban/server/test/it/qp/Map_NestedLoopsIT.java (+44/-0) src/test/java/com/akiban/sql/pg/PostgresServerPipelineSelectIT.java (+78/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/README.txt (+3/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/addresses.dat (+2/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/customers.dat (+3/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/items.dat (+6/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/orders.dat (+6/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/pipeline.properties (+5/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/schema.ddl (+44/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/select-1.expected (+4/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/select-1.sql (+3/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/select-3.expected (+3/-0) src/test/resources/com/akiban/sql/pg/pipeline-select/select-3.sql (+6/-0) |
To merge this branch: | bzr merge lp:~mmcm/akiban-server/sql-product-map-depth |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Thomas Jones-Low | Needs Fixing | ||
Nathan Williams | Approve | ||
Review via email: mp+177056@code.launchpad.net |
Description of the change
Fix depth setting for the left-deep Maps generated by Product.
They do not get deeper and deeper. Rather all but the first are one-deeper. This is different from the nested Maps for cross-product, which tend to be right-deep and so do get deeper.
To test this, and for the future, add a new Postgres IT that runs SQL queries with the pipeline options on.
Also add a Map IT for this kind of nesting, although it was already executing fine if the depths were consistent.
To post a comment you must log in.
Looks good.