[ 
https://issues.apache.org/jira/browse/CALCITE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292119#comment-14292119
 ] 

Aman Sinha commented on CALCITE-569:
------------------------------------

The patch looks ok to me based on the following observations: 
 - Since {{RelOptUtil.createProject()}} creates a LogicalProject with empty 
collation trait (not preserve), it is consistent with my previous observation 
that the IOBE was due to preserve.  
 - The refactoring to use the createProject() makes sense since it takes into 
account trivial projects.

Even with these changes, the unnecessary Sort appears at the root of the plan - 
can you check if SortRemoveRule is getting applied or not ?
I have updated the plan test to have the expected plan that contains exactly 1 
Sort and will upload the diff file.   This test will fail currently until the 
unnecessary Sort issue is resolved. 

> ArrayIndexOutOfBoundException when deducing collation
> -----------------------------------------------------
>
>                 Key: CALCITE-569
>                 URL: https://issues.apache.org/jira/browse/CALCITE-569
>             Project: Calcite
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating
>            Reporter: Aman Sinha
>            Assignee: Julian Hyde
>         Attachments: 
> 0001-CALCITE-569-Create-a-Project-with-empty-collation-if.patch, 
> 0001-Properly-track-collation-trait-for-select-a-from-.-o.patch
>
>
> If a subquery has an ORDER BY on a column that is not in the SELECT list and 
> the outer query does another ORDER BY,  Calcite encounters an 
> ArrayIndexOutOfBoundException when deducing collation. 
> In PlannerTest, I created a simple test by first adding the following traits: 
>  {code}
>           List<RelTraitDef> traitDefs = new ArrayList<RelTraitDef>();
>           traitDefs.add(ConventionTraitDef.INSTANCE);
>           traitDefs.add(RelCollationTraitDef.INSTANCE);
> {code}
> And ran the following query: 
> {code}
> select t.psPartkey from (select ps.psPartkey from `tpch`.`partsupp` ps order 
> by ps.psSupplyCost) t order by t.psPartkey"
> {code}
> {code}
> java.lang.ArrayIndexOutOfBoundsException: -1
>       at 
> org.apache.calcite.rex.RexProgram.deduceCollations(RexProgram.java:589)
>       at org.apache.calcite.rex.RexProgram.getCollations(RexProgram.java:558)
>       at 
> org.apache.calcite.plan.RelOptUtil.createProject(RelOptUtil.java:2685)
>       at 
> org.apache.calcite.plan.RelOptUtil.createProject(RelOptUtil.java:2623)
>       at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelectList(SqlToRelConverter.java:3571)
>       at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelectImpl(SqlToRelConverter.java:613)
>       at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelect(SqlToRelConverter.java:568)
>       at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:2929)
>       at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:526)
>       at org.apache.calcite.prepare.PlannerImpl.convert(PlannerImpl.java:189)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to