You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Ran Tao (Jira)" <ji...@apache.org> on 2023/09/25 11:40:00 UTC

[jira] [Commented] (CALCITE-6024) ListSqlOperatorTable is inefficient

    [ https://issues.apache.org/jira/browse/CALCITE-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768654#comment-17768654 ] 

Ran Tao commented on CALCITE-6024:
----------------------------------

+1 for this issue, I'm glad to fix this if it hasn't been started yet.

> ListSqlOperatorTable is inefficient
> -----------------------------------
>
>                 Key: CALCITE-6024
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6024
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Julian Hyde
>            Priority: Major
>
> {{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)