[
https://issues.apache.org/jira/browse/CALCITE-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-1062.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/c1ceba45 and
http://git-wip-us.apache.org/repos/asf/calcite/commit/72b2cfb7. Thanks for the
PR, [~seanhychu]!
> 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
> Fix For: 1.7.0
>
>
> 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)
