[
https://issues.apache.org/jira/browse/CALCITE-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454342#comment-16454342
]
Laurent Goujon commented on CALCITE-2282:
-----------------------------------------
[~sudheeshkatkam] maybe you can explain what problem you observed? If I
remember correctly, some functions/operators added to a different table/not
present in {{StdSqlOperatorTable}} might be unparsed differently if called
before functions are resolved?
[~julianhyde] if one wants to specify a different operator table for parsing,
would you rather prefer overriding method to access it, or would you prefer the
base class for the parser to be configurable in {{Parser.jj}} (which would give
even more flexibility)? Or maybe you have a 3rd proposal?
> 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
> Assignee: Julian Hyde
> 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)
