[
https://issues.apache.org/jira/browse/CALCITE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825802#comment-16825802
]
Hongze Zhang edited comment on CALCITE-2282 at 4/25/19 7:28 AM:
----------------------------------------------------------------
{quote}I didn't find the way as Hongze Zhang said to custom static built-in
operators without changing the parser for this use case.
{quote}
Maybe you can check the fix of CALCITE-1062, generally the functionality should
work for you. (That said, you can put a operator with same NAME, KIND to your
own table, then validator will use it to replace the original one)
was (Author: zhztheplayer):
{quote}I didn't find the way as Hongze Zhang said to custom static built-in
operators without changing the parser for this use case.{quote}
Maybe you can check the fix of CALCITE-1062, generally the functionality should
work for you.
> Allow OperatorTable to be pluggable in the parser
> -------------------------------------------------
>
> Key: CALCITE-2282
> URL: https://issues.apache.org/jira/browse/CALCITE-2282
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Sudheesh Katkam
> Priority: Major
> Attachments: CALCITE-2282.patch.txt
>
>
> SqlAbstractParserImpl [hardcodes OperatorTable to
> SqlStdOperatorTable|https://github.com/apache/calcite/blob/8327e674e7f0a768d124fa37fd75cda4b8a35bb6/core/src/main/java/org/apache/calcite/sql/parser/SqlAbstractParserImpl.java#L334|https://github.com/apache/calcite/blob/8327e674e7f0a768d124fa37fd75cda4b8a35bb6/core/src/main/java/org/apache/calcite/sql/parser/SqlAbstractParserImpl.java#L334].
> Make this pluggable via a protected method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
