[
https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maryann Xue updated PHOENIX-1489:
---------------------------------
Attachment: 1489-2.patch
Project multiple KeyValues to single KeyValue tuple on server side, the same
way it is done for join queries.
1. Added a client-side only PColumn implementation for projected column with
one specific field "sourceColumnRef".
2. Modified ProjectedTableColumnResolver for generalization and moved it from
JoinCompiler to FromCompiler.
3. Moved the tuple projection compilation from JoinCompiler to a separate file.
4. Aside from making projected tables for join queries, the
TupleProjectionCompiler visits single flat statement to extract columns to be
projected.
Including a small fix for getting display name in
LocalIndexDataColumnColumnRef.newColumnExpression()
> 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
>
>
> 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)
