[
https://issues.apache.org/jira/browse/PHOENIX-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247650#comment-14247650
]
Maryann Xue commented on PHOENIX-1533:
--------------------------------------
I see. Stop at "StatementContext.getScanRanges().isPointLookup()==true" makes
perfect sense. Thanks for the advice, [~giacomotaylor]! Before your
explanation, I didn't fully understand the point-lookup logic.
> 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
> 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)
