[
https://issues.apache.org/jira/browse/CALCITE-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038130#comment-18038130
]
Julian Hyde commented on CALCITE-4099:
--------------------------------------
{quote}Obviously it is bad to have SqlOperator so tightly connected to
RexImpTable but if we decide that want the mapping there to be the source of
truth we can extract it from RexImpTable and move it at the operator
instantiation (or elsewhere).{quote}
That sounds like a good plan. You didn't make the mistake of putting the
logical behavior (algebraic properties) of operators in a physical table (I
think it was me). This is a step in the right direction, so let's do it.
> Unify Strong.Policy and NullPolicy
> ----------------------------------
>
> Key: CALCITE-4099
> URL: https://issues.apache.org/jira/browse/CALCITE-4099
> Project: Calcite
> Issue Type: Task
> Components: core
> Reporter: Ruben Q L
> Priority: Minor
> Labels: pull-request-available
>
> (discussion about this ticket started in CALCITE-4094)
> {{Strong.Policy}} and {{NullPolicy}} are two different enum that represent
> grosso-modo the same thing. The former is mostly used on the simplifier, and
> the latter on the code generation.
> To be studied if we could unify both entities and make it available through
> the SqlOperator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
