[
https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338826#comment-14338826
]
James Taylor commented on PHOENIX-1489:
---------------------------------------
Compatibility means a mix of old and new clients both working against new
server. The server is always upgraded first. For more, see here:
http://phoenix.apache.org/upgrading.html
I can see how it'd be possible to make this b/w compatible, but might not be
worth it. I think it's ok if this change is targeted for the next major release
(especially if it let's us move quicker).
> 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)
