You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2019/01/31 05:48:00 UTC

[jira] [Updated] (PHOENIX-5116) DistinctPrefixFilterIT fails.

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

Lars Hofhansl updated PHOENIX-5116:
-----------------------------------
    Summary: DistinctPrefixFilterIT fails.  (was: DistinctPrefixFilterIT)

> DistinctPrefixFilterIT fails.
> -----------------------------
>
>                 Key: PHOENIX-5116
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5116
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Lars Hofhansl
>            Priority: Major
>         Attachments: 5116.txt
>
>
> Caused by this scenario outlined on PHOENIX-5109:
> {quote}
> This just does not end. Now there's a special case for the following:
> *     compound key of VARCHAR
> *     SELECT DISTINCT <prefix of the key>
> *     Salting is enabled
> *     There is a local index on an unrelated column
> Now Phoenix selects a full local index scan, which is heuristically less efficient... I think.
> The problem is that there are cases where a plan for a salted table nonetheless gets a key range that is not salted - does not have the salt range in it. That throws the logic off in this case.
> {quote}



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