[
https://issues.apache.org/jira/browse/PHOENIX-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251403#comment-14251403
]
Kristoffer Sjögren commented on PHOENIX-1489:
---------------------------------------------
We have noticed that both qualifier name and value are transferred from region
server to client, for all column values and rows during scan queries.
For us, sometimes this is especially bad for tables which have 2-3 column keys
and 20-25 column values. And the problem gets worse when column value names are
very descriptive, i.e. sometimes 20-30 characters long.
1) With this fix, I suppose that each scan result will contain the value along
with a 4(?) byte position/offset per column value instead of the actual column
name?
2) I did not see column names transfer for row keys, so I guess there is no
overhead for row key columns?
> 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-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)
