[
https://issues.apache.org/jira/browse/PHOENIX-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341163#comment-15341163
]
James Taylor commented on PHOENIX-3012:
---------------------------------------
Touch base with Mujtaba tomorrow - it might not be related.
For the merge sort, I think you've found the cause. In AggregatePlan, it
doesn't look like it's using an offset of SaltingUtil.NUM_SALTING_BYTES for the
merge sort if salted (FYI, for local indexes, the key prefix is stripped on the
server-side):
{code}
aggResultIterator = new GroupedAggregatingResultIterator(new
MergeSortRowKeyResultIterator(iterators), aggregators);
{code}
It should use the other constructor of MergeSortRowKeyResultIterator that takes
an offset.
Does the local index case work now with your patch?
> DistinctPrefixFilter logic fails with local indexes and salted tables
> ---------------------------------------------------------------------
>
> Key: PHOENIX-3012
> URL: https://issues.apache.org/jira/browse/PHOENIX-3012
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Lars Hofhansl
> Priority: Critical
> Fix For: 4.8.0
>
> Attachments: 3012-does.not.work.txt
>
>
> Arrghhh... Another case where there are issues.
> With local indexes parents (PHOENIX-258) does not work.
> I do not understand enough about local indexes to say why offhand, only that
> it appears to be broken.
> I'll look.Might be best to turn this off for local indexes for now (if that's
> easy to detect) while I figure this out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
