[
https://issues.apache.org/jira/browse/CALCITE-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883792#comment-17883792
]
Mingcan Wang commented on CALCITE-6161:
---------------------------------------
Hello, [~asolimando], I am sorry that this issue has been shelved due to my
own reason. This will not block the release of 1.38. You can remove the fixed
version for now. I will continue to follow up on this issue in October.
> The equalsDeep of sqlCall should compare sqlOperator's sqlKind
> --------------------------------------------------------------
>
> Key: CALCITE-6161
> URL: https://issues.apache.org/jira/browse/CALCITE-6161
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.36.0
> Reporter: Mingcan Wang
> Assignee: Mingcan Wang
> Priority: Minor
> Labels: pull-request-available
>
> Here is the situation:
> when I create two SqlBasicCalls, one uses UNARY_MINUS operator and the other
> uses MINUS operator. But their operandList is the same. However, The result
> after calling their equalsDeep() method is true.
> I found that the sqlKind of many operators is reused, and the name is not
> guaranteed to be unique. Only the combination of kind and name can determine
> the unique operator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
