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

Thomas D'Silva updated PHOENIX-2075:
------------------------------------
    Attachment: PHOENIX-2075-4.4-HBase-0.98-v2.patch

I removed the pom changes and will fix that as as part of 
https://issues.apache.org/jira/browse/PHOENIX-2085

AggregatePlan, UnionPlan still don't use the ParallelScanGrouper that is passed 
in, but these queries are not supported by our map reduce implementation 
currently. 

> MR integration uses single mapper unless table is salted
> --------------------------------------------------------
>
>                 Key: PHOENIX-2075
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2075
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Thomas D'Silva
>         Attachments: PHOENIX-2075-4.4-HBase-0.98-v2.patch, 
> PHOENIX-2075-4.4-HBase-0.98.patch
>
>
> Due to the way we interpret the scans, when we read data from our MR 
> integration, it's always processed by a single mapper.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to