[
https://issues.apache.org/jira/browse/CALCITE-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780566#comment-17780566
]
Julian Hyde edited comment on CALCITE-6024 at 10/28/23 12:12 AM:
-----------------------------------------------------------------
Fixed in
[7b9660f1|https://github.com/apache/calcite/commit/7b9660f150e66c544ce8df47015978b39f40e7e4].
(Thanks for the review, [~libenchao]!)
was (Author: julianhyde):
Fixed in
[7b9660f1|https://github.com/apache/calcite/commit/7b9660f150e66c544ce8df47015978b39f40e7e4].
> A more efficient implementation of SqlOperatorTable, backed by an immutable
> multi-map keyed by upper-case operator name
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-6024
> URL: https://issues.apache.org/jira/browse/CALCITE-6024
> Project: Calcite
> Issue Type: Improvement
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.36.0
>
>
> {{ListSqlOperatorTable}} is inefficient if it contains a large number of
> operators. It currently examines the operators one by one.
> {{ReflectiveSqlOperatorTable}} (and its subclass, {{SqlStdOperatorTable}})
> builds a map of operators by name (actually two maps, one case-sensitive and
> one case-insensitive).
> {{ListSqlOperatorTable}} should do the same, at least in its immutable form.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
