[
https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344301#comment-14344301
]
James Taylor commented on PHOENIX-1489:
---------------------------------------
Thanks, [~maryannxue]. Would a mix of new and old clients in 4.0 work against
an updated server now? With your change, does projector = null for the b/w
compat case here (and thus the results don't end up getting put into a single
cell)?
{code}
+ if (projector != null) {
+ Tuple tuple = projector.projectResults(new
ResultTuple(Result.create(result)));
+ result.clear();
+ result.add(tuple.getValue(0));
+ }
{code}
> 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)
