[
https://issues.apache.org/jira/browse/CALCITE-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18011371#comment-18011371
]
Zhen Chen commented on CALCITE-7117:
------------------------------------
[~h19735] I suspect you're referring to Apache Ignite, which uses Calcite for
SQL parsing and optimization, but doesn't seem to use the Calcite executor. If
the issue is related to suboptimal Calcite planning, you could provide
information about the current plan and your desired plan. As for simply slow
execution, I think you should analyze the metrics in Ignite to initially
identify the issue.
> Ignite is particularly slow when executing multi field IN, such as (column1,
> column2) in (xxx, xxx), (xxx, xxx)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-7117
> URL: https://issues.apache.org/jira/browse/CALCITE-7117
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.37.0
> Reporter: FENG WANG
> Priority: Major
>
> I would like to provide feedback on an issue regarding ignite calcite, which
> is particularly slow when executing multi field IN, such as (column1,
> column2) in (xxx, xxx), (xxx, xxx)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
