phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-5116) DistinctPrefixFilterIT
Date Thu, 31 Jan 2019 05:45:00 GMT
Lars Hofhansl created PHOENIX-5116:
--------------------------------------

             Summary: DistinctPrefixFilterIT
                 Key: PHOENIX-5116
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5116
             Project: Phoenix
          Issue Type: Task
            Reporter: Lars Hofhansl


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)

Mime
View raw message