phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-1533) Last key part not taken into child/parent optimization
Date Wed, 21 Jan 2015 03:44:34 GMT

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

Maryann Xue resolved PHOENIX-1533.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.3
                   4.3

> Last key part not taken into child/parent optimization
> ------------------------------------------------------
>
>                 Key: PHOENIX-1533
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1533
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 4.0.0, 5.0.0
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>             Fix For: 4.3, 3.3
>
>         Attachments: 1533.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> For example we have multiple PK columns (pk0, pk1, pk2) for table A, if we do a IN subquery
or join query with all PK columns, like:
> select * from A where (pk0, pk1, pk2) IN (select pk0, pk1, pk2 from B);
> The child/parent join optimization is supposed to use the entire PK "(pk0, pk1, pk2)"
for constructing the dynamic skip-scan filter.
> However it would only use (pk0, pk1) instead, missing the last PK part.



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

Mime
View raw message