phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-3328) Optimize ORed leading pk column range comparisions to SkipScan
Date Wed, 26 Oct 2016 00:08:58 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated PHOENIX-3328:
----------------------------------
    Fix Version/s:     (was: 4.8.2)

> Optimize ORed leading pk column range comparisions to SkipScan
> --------------------------------------------------------------
>
>                 Key: PHOENIX-3328
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3328
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: William Yang
>            Assignee: William Yang
>            Priority: Minor
>             Fix For: 4.9.0
>
>         Attachments: PHOENIX-3328.patch
>
>
> {code:sql}
> create table t1 (pk integer primary key, a integer);
> create table t2 (pk1 integer not null, pk2 integer not null, a integer constraint pk
primary key (pk1, pk2));
> explain select * from t1 where (pk > 10 and pk < 20) or (pk > 30 and pk <
40);
> explain select * from t2 where (pk1 > 10 and pk1 < 20) or (pk1 > 30 and pk1
< 40);
> {code}
> The first SELECT statement will use skip scan filter for two ranges, so as the second
one. But actually the WhereOptimizer failed doing so and using a full table scan instead.
This happens for tables have multi PK columns.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message