[
https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345625#comment-14345625
]
Hudson commented on PHOENIX-1489:
---------------------------------
SUCCESS: Integrated in Phoenix-master #603 (See
[https://builds.apache.org/job/Phoenix-master/603/])
PHOENIX-1489 Access column values positionally from client (maryannxue: rev
3f829751dd5158c526e5c5bd3da61dde1c6e4194)
*
phoenix-core/src/it/java/org/apache/phoenix/end2end/SubqueryUsingSortMergeJoinIT.java
* phoenix-core/src/main/java/org/apache/phoenix/join/HashJoinInfo.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/ProjectedColumn.java
* phoenix-core/src/main/java/org/apache/phoenix/optimize/QueryOptimizer.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/JoinCompiler.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/ExpressionCompiler.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/HashJoinIT.java
*
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/GlobalIndexOptimizationIT.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/OrderByCompiler.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/TableRef.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/TupleProjector.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/HashJoinRegionScanner.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/BaseScannerRegionObserver.java
*
phoenix-core/src/main/java/org/apache/phoenix/compile/TupleProjectionCompiler.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/SubqueryIT.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/HashJoinLocalIndexIT.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/WhereCompiler.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/index/LocalIndexIT.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/GroupedAggregateRegionObserver.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/ProjectionCompiler.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/PTableType.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/FromCompiler.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/UpsertCompiler.java
* phoenix-core/src/test/java/org/apache/phoenix/compile/WhereCompilerTest.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/ColumnRef.java
*
phoenix-core/src/main/java/org/apache/phoenix/schema/LocalIndexDataColumnRef.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/ScanRegionObserver.java
> Access column values positionally from client
> ---------------------------------------------
>
> Key: PHOENIX-1489
> URL: https://issues.apache.org/jira/browse/PHOENIX-1489
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Maryann Xue
> Attachments: 1489-2.patch, 1489-v1.patch, 1489-v3.patch, 1489-v4.patch
>
>
> Instead of passing back separate KeyValues for data returned from the server,
> we should access via position using our TupleProjector everywhere. This is
> already the case for joins and aggregate queries, but not for scan queries.
> We can modify ScanRegionObserver to use our KeyValueSchema to accomplish this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)