You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2021/04/29 11:09:00 UTC
[jira] [Commented] (IGNITE-13710) Calcite integration. Fix or to
union rule logic
[ https://issues.apache.org/jira/browse/IGNITE-13710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335366#comment-17335366 ]
Aleksey Plekhanov commented on IGNITE-13710:
--------------------------------------------
Since Calcite version 1.26, {{OR}} operator on the same field replaced with {{SEARCH}} operator. If we will try to replace each {{SEARCH}} by {{UNION}}, there will be too many plan variants, since other operators can also be translated to search (for example {{a != n}} can be replaced by {{SEARCH}} with two ranges {{[-infinity, n)}} and {{(n, infinity]}}). I think it's better to add native {{SEARCH}} support with the ability to scan indexes using {{SEARCH}} operator.
> Calcite integration. Fix or to union rule logic
> -----------------------------------------------
>
> Key: IGNITE-13710
> URL: https://issues.apache.org/jira/browse/IGNITE-13710
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Igor Seliverstov
> Assignee: Aleksey Plekhanov
> Priority: Minor
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)