asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ildar Absalyamov (Code Review)" <>
Subject Change in asterixdb[release-0.8.8]: ASTERIXDB-1221: - Fixed test regression and improved plans ...
Date Fri, 11 Dec 2015 22:43:10 GMT
Ildar Absalyamov has posted comments on this change.

Change subject: ASTERIXDB-1221:  - Fixed test regression and improved plans in insert\delete

Patch Set 2:

File asterix-algebra/src/main/java/org/apache/asterix/optimizer/rules/

Line 147
> Why the piece of code is no longer needed?
Again leftover from previous version of patch
This was an attempt to remove usages of context.addPrimaryKey/findPrimaryKey
File asterix-algebra/src/main/java/org/apache/asterix/optimizer/rules/

Line 56:  *         ============
> I'm not sure why this rule is needed. It seems to be the inverse of InlineV
True, seems like it does the opposite. But we do already have a rule which does exactly that:
ExtractCommonExpressionsRule, right?
Maybe the right solution here would be to make ExtractCommonExpressionsRule aware of equivalence

Also note that the purpose of the rule was not only to put the right connector, but reuse
common subexpressions, which are extracting PK from the record.
File asterix-app/src/main/java/org/apache/asterix/aql/translator/

Line 952:             //check whether there exists another enforced index on the same field
> Why does it matter?
This is done to allow creating multiple open indexes with promotable types. See negative test
case runtimets/queries/open-index-enforced/error-checking/index-type-promotion-collision/index-type-promotion-collision.1.ddl.aql
for reference.
I guess I'll better file a separate issue and patch for that
File asterix-app/src/test/resources/optimizerts/queries/scan-insert-secondary-index.aql:

Line 49
> Why do you delete this test case?
This test case was kinda superseded by asterix-app/src/test/resources/optimizerts/queries/scan-insert-secondary-index-btree.aql
File asterix-app/src/test/resources/runtimets/queries/dml/insert-and-scan-dataset-with-index-on-open-field/insert-and-scan-dataset-with-index-on-open-field.1.ddl.aql:

Line 33: age:int64,
> why int32 does not work?
I've changed this test case was accidentally omitted (not included into testsuite) and missed
the transition to int64 being default integer type.
Query with int32 would have perfectly worked, but the adm result which would be produced would
contain ugly "i32" suffixes in all integer fields.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: I304955b79c5813f7b99539da674ab519e124aae4
Gerrit-PatchSet: 2
Gerrit-Project: asterixdb
Gerrit-Branch: release-0.8.8
Gerrit-Owner: Ildar Absalyamov <>
Gerrit-Reviewer: Ildar Absalyamov <>
Gerrit-Reviewer: Jenkins <>
Gerrit-Reviewer: Yingyi Bu <>
Gerrit-HasComments: Yes

View raw message