[
https://issues.apache.org/jira/browse/CALCITE-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803624#comment-16803624
]
Danny Chan commented on CALCITE-2960:
-------------------------------------
BTW, i never saw any case that Calcite use CalciteCatalogReader to look up
operators, it only use it for table name resolving. For operators, Calcite
actually use SqlOperatorTable, please correct me if i'm wrong.
> CalciteCatalogReader use a hard-coding config to get functions
> --------------------------------------------------------------
>
> Key: CALCITE-2960
> URL: https://issues.apache.org/jira/browse/CALCITE-2960
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.18.0
> Reporter: Lai Zhou
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CalciteCatalogReader use a hard-coding config to get functions
> {code:java}
> functions2.addAll(schema.getFunctions(name, true));
> {code}
> the right way is：
> {code:java}
> functions2.addAll(schema.getFunctions(name, config.caseSensitive()));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
