You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2016/11/28 11:18:58 UTC
[jira] [Commented] (FLINK-4825) Implement a RexExecutor that uses
Flink's code generation
[ https://issues.apache.org/jira/browse/FLINK-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701687#comment-15701687 ]
Timo Walther commented on FLINK-4825:
-------------------------------------
[~jark] unfortunately, there many other issues than just {{TRUE/true}} e.g. when using POJOs.
> Implement a RexExecutor that uses Flink's code generation
> ---------------------------------------------------------
>
> Key: FLINK-4825
> URL: https://issues.apache.org/jira/browse/FLINK-4825
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Timo Walther
>
> The added {{ReduceExpressionRule}} leads to inconsistent behavior. Because some parts of an expression are evalutated using Flink's code generation and some parts use Calcite's code generation.
> A very easy example: boolean expressions casted to string are represented as "TRUE/FALSE" using Calcite and "true/false" using Flink.
> I propose to implement the RexExecutor interface and forward the calls to Flink's code generation. Additional improvements in order to be more standard compliant could be solved in new Jira issues.
> I will disable the rule and the corresponding tests till this issue is fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)