[
https://issues.apache.org/jira/browse/CALCITE-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde reopened CALCITE-2736:
----------------------------------
Regardless of which release it goes into, the change is producing warnings
relating to calls to deprecated APIs, so it shouldn't be in master. I have put
it onto a branch https://github.com/julianhyde/calcite/tree/2736-reduce-options
and force-pushed to remove it from master. Let's merge it after the release,
and after the warnings are fixed.
Policy is to release from master, not a spur. It produces a simple change log,
and holding back merges around release time is not too onerous for a project of
this velocity.
I don't want even minor changes to be added to this RC. Hive's regress is in
progress, and takes several days.
> ReduceExpressionsRule never reduces dynamic expressions but this should be
> configurable
> ---------------------------------------------------------------------------------------
>
> Key: CALCITE-2736
> URL: https://issues.apache.org/jira/browse/CALCITE-2736
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Jacques Nadeau
> Assignee: Jacques Nadeau
> Priority: Major
> Fix For: 1.19.0
>
>
> There are situations where it is helpful to reduce dynamic SqlCalls. Right
> now, the ReduceExpressionsRule always avoids doing this. We should enhance
> the rule so this can be configurable depending on where in planning the rule
> is used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
