You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Maryann Xue (JIRA)" <ji...@apache.org> on 2015/02/20 17:39:13 UTC

[jira] [Issue Comment Deleted] (PHOENIX-1489) Access column values positionally from client

     [ https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maryann Xue updated PHOENIX-1489:
---------------------------------
    Comment: was deleted

(was: There is one thing incompatible: I removed the "forceProjection" flag from HashJoinInfo, which itself does not break the backward compatibility coz we still serialize/deserialize a dummy flag. But that logic has been removed from HashJoinRegionServer for code simplicity and efficiency. Think I can make it compatible just by restoring those two files.)

> 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)