phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5116) DistinctPrefixFilterIT fails.
Date Thu, 31 Jan 2019 05:49:00 GMT


Lars Hofhansl commented on PHOENIX-5116:

Instead of the table, I had to check the plan whether it has salted key-ranges, and in that
case remove those from consideration in choosing a plan.

The change as such should be very uncontroversial. I can LocalIndexIT and DistinctPrefixFilterIT,
both pass now.

> DistinctPrefixFilterIT fails.
> -----------------------------
>                 Key: PHOENIX-5116
>                 URL:
>             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

View raw message