[jira] [Commented] (PHOENIX-2075) MR integration uses single mapper unless table is salted

[James Taylor (JIRA)]

    [ 
https://issues.apache.org/jira/browse/PHOENIX-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603735#comment-14603735
 ] 

James Taylor commented on PHOENIX-2075:
---------------------------------------

Also, maybe not relevant for MR, but seems like we're losing the state of 
passing through a different impl here:
{code}
diff --git 
a/phoenix-core/src/main/java/org/apache/phoenix/execute/UnionPlan.java 
b/phoenix-core/src/main/java/org/apache/phoenix/execute/UnionPlan.java
index 031b58b..4406275 100644
--- a/phoenix-core/src/main/java/org/apache/phoenix/execute/UnionPlan.java
+++ b/phoenix-core/src/main/java/org/apache/phoenix/execute/UnionPlan.java
@@ -34,6 +34,7 @@ import org.apache.phoenix.compile.StatementContext;
 import org.apache.phoenix.iterate.ConcatResultIterator;
 import org.apache.phoenix.iterate.LimitingResultIterator;
 import org.apache.phoenix.iterate.MergeSortTopNResultIterator;
+import org.apache.phoenix.iterate.ParallelScanGrouper;
 import org.apache.phoenix.iterate.ResultIterator;
 import org.apache.phoenix.iterate.UnionResultIterators;
 import org.apache.phoenix.parse.FilterableStatement;
@@ -123,6 +124,11 @@ public class UnionPlan implements QueryPlan {
     }
 
     @Override
+    public final ResultIterator iterator(ParallelScanGrouper scanGrouper) 
throws SQLException {
+        return iterator(Collections.<SQLCloseable>emptyList());
+    }
+    
+    @Override
{code}
and here:
{code}
diff --git 
a/phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixStatement.java 
b/phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixStatement.java
index 51fb027..8843486 100644
--- a/phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixStatement.java
+++ b/phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixStatement.java
@@ -70,6 +70,7 @@ import org.apache.phoenix.exception.SQLExceptionInfo;
 import org.apache.phoenix.execute.MutationState;
 import org.apache.phoenix.expression.RowKeyColumnExpression;
 import org.apache.phoenix.iterate.MaterializedResultIterator;
+import org.apache.phoenix.iterate.ParallelScanGrouper;
 import org.apache.phoenix.iterate.ResultIterator;
 import org.apache.phoenix.parse.AddColumnStatement;
 import org.apache.phoenix.parse.AliasedNode;
@@ -441,6 +442,11 @@ public class PhoenixStatement implements Statement, 
SQLCloseable, org.apache.pho
                 public ResultIterator iterator() throws SQLException {
                     return iterator;
                 }
+                
+                @Override
+                public ResultIterator iterator(ParallelScanGrouper 
scanGrouper) throws SQLException {
+                    return iterator;
+                }
 
{code}
Not sure if we can easily thread this through in these places or not.

> 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.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)