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-627) Optimize fully qualified OR expressions as we do for IN expressions
Date Sat, 23 Aug 2014 05:20:10 GMT

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

James Taylor updated PHOENIX-627:
---------------------------------

    Assignee: Kyle Buzsaki  (was: James Taylor)

> Optimize fully qualified OR expressions as we do for IN expressions
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-627
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-627
>             Project: Phoenix
>          Issue Type: Task
>    Affects Versions: 3.0-Release
>            Reporter: James Taylor
>            Assignee: Kyle Buzsaki
>
> Assume you have a schema like this:
>     CREATE TABLE t (a INTEGER, b INTEGER CONSTRAINT pk PRIMARY KEY (a,b))
> We currently optimize the following to be a series of point gets through our skip scan
filter:
>     SELECT * FROM t WHERE (a,b) IN ((1,2), (3,4), (5,6))
> However, we don't to the same for a query like this:
>     SELECT * FROM t WHERE (a = 1 AND b = 2) OR (a = 3 AND b=4) OR (a=5 AND b=6)
> This change would be completely isolated to the the following method on WhereOptimizer.KeyExpressionVisitor:
>         private KeySlots orKeySlots(OrExpression orExpression, List<KeySlots> childSlots)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message