[
https://issues.apache.org/jira/browse/IGNITE-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-13568:
---------------------------------------
Description: As of now, we analyze just the first column from predicate to
detemine lower and upper bounds for complex indexes in case first predicate is
not equal. It decreasing search space, however for particular cases, it could
be not so effective, for example, the selectivity of the first column is very
low. We need to take into account all columns from predicate and suitable
index. Need to keep in mind that each column at the index could be sorted in a
different manner. (was: As of now, we analyze just the first column from
predicate to detemine lower and upper bounds for complex indexes. It decreasing
search space, however for particular cases, it could be not so effective, for
example, the selectivity of the first column is very low. We need to take into
account all columns from predicate and suitable index. Need to keep in mind
that each column at the index could be sorted in a different manner.)
> Calcite integration. Decrease bounds of index scan
> --------------------------------------------------
>
> Key: IGNITE-13568
> URL: https://issues.apache.org/jira/browse/IGNITE-13568
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Priority: Major
>
> As of now, we analyze just the first column from predicate to detemine lower
> and upper bounds for complex indexes in case first predicate is not equal. It
> decreasing search space, however for particular cases, it could be not so
> effective, for example, the selectivity of the first column is very low. We
> need to take into account all columns from predicate and suitable index. Need
> to keep in mind that each column at the index could be sorted in a different
> manner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
