[
https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510398#comment-14510398
]
Hudson commented on PHOENIX-1489:
---------------------------------
FAILURE: Integrated in Phoenix-master #714 (See
[https://builds.apache.org/job/Phoenix-master/714/])
PHOENIX-1773 Backward compatibility for joins fail after PHOENIX-1489
(maryannxue: rev 124ab6db0b95fb30b287e1dfb2a626bd95546219)
* phoenix-core/src/main/java/org/apache/phoenix/join/HashJoinInfo.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
> Fix For: 4.4.0
>
> 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)
