You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Anton Mushin (JIRA)" <ji...@apache.org> on 2017/02/07 09:44:42 UTC
[jira] [Commented] (FLINK-5435) Cleanup the rules introduced by
FLINK-5144 when calcite releases 1.12
[ https://issues.apache.org/jira/browse/FLINK-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855653#comment-15855653 ]
Anton Mushin commented on FLINK-5435:
-------------------------------------
Hi.
We have problem in FLINK-5435 with calcite rule. In PR for FLINK-5435 I use work around - the copy of rule inside Flink with changes.
For fix the problem in calcite I created jira issue: CALCITE-1621
I think that will be correct clean up the FlinkAggregateReduceFunctionsRule in this issue.
What do you think about it?
> Cleanup the rules introduced by FLINK-5144 when calcite releases 1.12
> ---------------------------------------------------------------------
>
> Key: FLINK-5435
> URL: https://issues.apache.org/jira/browse/FLINK-5435
> Project: Flink
> Issue Type: Task
> Components: Table API & SQL
> Reporter: Kurt Young
> Assignee: Kurt Young
> Priority: Minor
>
> When fixing https://issues.apache.org/jira/browse/FLINK-5144, we actually copied some classes from Calcite and do a quick fix in Flink. The fixing is actually merged by Calcite and will be included in version 1.12, we should update the Calcite version and remove the classes we copied.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)