[
https://issues.apache.org/jira/browse/CALCITE-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878987#comment-15878987
]
Julian Hyde commented on CALCITE-1653:
--------------------------------------
[~jcamachorodriguez], See my comments on CALCITE-1417 about why we can't use
the planner's executor. Basically, there are life-cycle issues; there might not
be a planner available yet. CALCITE-1536 will improve life cycle issues but we
still might decide to not use the (expensive) full executor at every point in
the query preparation process. For instance, at sql-to-rel time, we might use a
simple executor that refuses to simplify {{CAST(string AS DATE)}}.
> Allow for custom RelOptPlanner.Executor in RexUtil.simplify
> -----------------------------------------------------------
>
> Key: CALCITE-1653
> URL: https://issues.apache.org/jira/browse/CALCITE-1653
> Project: Calcite
> Issue Type: Bug
> Reporter: Remus Rusanu
> Assignee: Remus Rusanu
> Attachments: CALCITE-1653.00.patch
>
>
> {{RexUtil.simplify}} (and derivatives) use a default {{EXECUTOR}} for
> evaluating literals and expression in {{simplifyCast}}. This causes value
> differences from Hive, triggering issues like CALCITE-1650, CALCITE-1651.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
