[
https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3195:
----------------------------------
Attachment: PHOENIX-3195_partial.patch
[~lhofhansl] - here's a patch that'll fix the test failure. Though the ORDER BY
is compiled out, it's still projecting the column references it finds in the
scan. That's why it thinks the column family needs to be projected. This patch
addresses that - feel free to commit.
> Slight safety improvement for using DistinctPrefixFilter
> --------------------------------------------------------
>
> Key: PHOENIX-3195
> URL: https://issues.apache.org/jira/browse/PHOENIX-3195
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Minor
> Fix For: 4.9.0, 4.8.1
>
> Attachments: 3195.txt, PHOENIX-3195_partial.patch
>
>
> There is a very slight improvement to when we should use the
> DistinctPrefixFilter in its current form.
> Currently we check for the absence of WhereConditions, but what we really
> mean to make sure that only one Cell per row is seen. Phoenix already does
> that and used the FirstKeyOnlyFilter in that case. It's best to use this
> condition as well, just to be absolutely safe.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
