[
https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376792#comment-14376792
]
Mujtaba Chohan commented on PHOENIX-1489:
-----------------------------------------
[~maryannxue] Backward compatibility issue, with client on *Phoenix v4.2.1* and
server with Phoenix version after PHOENIX-1488 commit, no rows are returned in
resultset to the client for join queries.
> 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)
