[
https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337462#comment-14337462
]
Maryann Xue commented on PHOENIX-1489:
--------------------------------------
The bug fix is file as PHOENIX-1686,
I thought it was new client vs. old server. If it is the old client vs. new
server, it still can be made compatible, but it would require rolling back most
changes in HashRegionScanner.java. The server side only flatten KeyValues as
specified by a certain scan attributed. If it's an old client, the attribute
won't be set at all, and the server won't do anything other than return KVs as
they are.
So compatibility here actually means old client and new server or both ways? Is
there any way to test compatibility against all UTs?
> 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
>
>
> 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)
