[
https://issues.apache.org/jira/browse/CALCITE-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038116#comment-18038116
]
Stamatis Zampetakis commented on CALCITE-4099:
----------------------------------------------
I created a PR with a proof of concept that passes unit tests and demonstrates
what happens if we use everywhere the NullPolicy defined in RexImpTable.
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).
Apart from that I am still thinking which enum is better to retain (NullPolicy
or Strong.Policy) but haven't fully made up my mind.
> 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
>
> (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)
