[
https://issues.apache.org/jira/browse/CALCITE-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038013#comment-18038013
]
Stamatis Zampetakis commented on CALCITE-4099:
----------------------------------------------
I experimented a bit with the unification approach leaning towards exposing
{{NullPolicy}} or potentially a new API via the operator.
{code:java}
public class SqlOperator {
NullPolicy getNullPolicy();
}
{code}
One point that I am rather skeptical about is the mapping between an operator
and the {{NullPolicy}} that is defined in {{{}RexImpTable{}}}. By bringing the
{{NullPolicy}} to the {{SqlOperator}} interface it seems rather natural to move
the mapping from {{RexImpTable}} to the instantiation of each operator. This
will be quite some manual work and will create a large diff so I was wondering
how others feel with this approach.
> 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)
