phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-3157) Refactor DistinctPrefixFilter as filter wrapper so that it can work with non-pk column filters.
Date Fri, 18 Jan 2019 22:14:00 GMT

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

Thomas D'Silva updated PHOENIX-3157:
------------------------------------
    Fix Version/s:     (was: 4.15.0)

> Refactor DistinctPrefixFilter as filter wrapper so that it can work with non-pk column
filters.
> -----------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3157
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3157
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Lars Hofhansl
>            Priority: Major
>         Attachments: 3157-DOES_NOT_WORK.txt
>
>
> See PHOENIX-3156. The issue is pretty tricky:
> # only filterKeyValue can make skip decision
> # we're skiping rows (not Cells)
> # the next Cell we skip to is dynamic (not know ahead of time)
> # we can only skip if the row as a whole has not been filtered
> So in order to support non-pk column filters with this optimization (i.e. SELECT DISTINCT(pk1-prefix)
FROM table WHERE non-pk-column = xxx) we need to refashion this is FilterWrapper and only
fire the optimization when the inner filter did not filter the entire row, this is in many
cases hard to determine. It's certainly more complex than the TransactionVisibilityFilter.
> [~giacomotaylor]



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

Mime
View raw message