phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Poon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5096) Local index region pruning is not working as expected.
Date Thu, 10 Jan 2019 23:57:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739882#comment-16739882
] 

Vincent Poon commented on PHOENIX-5096:
---------------------------------------

Yea, the code looks wrong.  computeColumnsInCommon() doesn't look at the filter columns -
it always just returns the same result based on how the index is defined.

Looks like the code right now can best be described as something like "filter based on common
prefix", as in literally the same prefix between base and index rowkeys.

Which is not what PHOENIX-3941 was supposed to implement - "Filter based on data table leading
pk filter conditions"

> Local index region pruning is not working as expected.
> ------------------------------------------------------
>
>                 Key: PHOENIX-5096
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5096
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Priority: Major
>
> The pruning of local indexes should do the following:
> * Use the local index
> * Reduce the number of regions based on filters on the table's primary key (i.e. WHERE
conditions including prefixes of the primary key)
> Instead it looks like in order for this to work the needed PK column need to be included
in the local index itself, changing the sort order of the local index.
> I'll provide some examples in the comments.
> [~giacomotaylor], [~tdsilva], [~vincentpoon], [~elserj], [~gjacoby]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message