[
https://issues.apache.org/jira/browse/CALCITE-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122288#comment-15122288
]
Julian Hyde commented on CALCITE-1062:
--------------------------------------
But why add all this new code? Anyone can supply a custom implementation of
SqlOperatorTable and use it in the validator. That already works, AFAIK.
> Allowing SqlOperator to be overridden in validation
> ---------------------------------------------------
>
> Key: CALCITE-1062
> URL: https://issues.apache.org/jira/browse/CALCITE-1062
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Sean Hsuan-Yi Chu
> Assignee: Sean Hsuan-Yi Chu
>
> Calcite allows function to be overridden at validation step. To be more
> specific, users can provide their SqlOperatorTable, and, at validation step,
> their SqlOperatorTable will be called (method: lookupOperatorOverloads) to
> get a overriding function. However, so far, SqlOperator (e.g., +, - , *,
> etc.) does not have this mechanism yet.
> Since other systems (e.g., Apache Drill) would have more flexible type-checks
> for SqlOperator's operands, this mechanism is necessary for those systems to
> pass through the validation step.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
