You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2019/08/29 18:07:00 UTC

[jira] [Commented] (CALCITE-3297) PigToSqlAggregateRule should be applied on multi-set projection to produce an optimal plan

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

Julian Hyde commented on CALCITE-3297:
--------------------------------------

[~IhorHuzenko], Thanks for the rapid response, and reviewing your fix now. 

[~khaitran], Please review also.

> PigToSqlAggregateRule should be applied on multi-set projection to produce an optimal plan
> ------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-3297
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3297
>             Project: Calcite
>          Issue Type: Bug
>          Components: piglet
>            Reporter: Khai Tran
>            Assignee: Igor Guzenko
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.21.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Fixed testMultisetProjection() in PigRelOpTest.java to make sure the PigToSqlAggregateRule is applied to produce an optimized plan for doing multiset projection after COLLECT() agg func.
> The optimization rule was blocked by change in CALCITE-3138.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)