[ 
https://issues.apache.org/jira/browse/HBASE-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036448#comment-16036448
 ] 

Karan Mehta edited comment on HBASE-18097 at 6/7/17 6:06 PM:
-------------------------------------------------------------

The problem can occur if the client wants results in a specified batch size, in 
which case, the results can contain multiple partial results, which is then 
left to the user to handle appropriately, based on the {{partial}} flag inside 
the result. This is usually the case with AsyncHBaseClient.
Any suggestions, [~enis] or [~Apache9] ?


was (Author: karanmehta93):
The problem can occur if the client wants results in a specified batch size, in 
which case, the results can contain multiple partial results, which is then 
left to the user to handle appropriately, based on the {{partial}} flag inside 
the result. This is usually the case with AsyncHBaseClient.

> Save bandwidth on partial_flag_per_result in ScanResponse proto
> ---------------------------------------------------------------
>
>                 Key: HBASE-18097
>                 URL: https://issues.apache.org/jira/browse/HBASE-18097
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0, 1.4.0
>            Reporter: Karan Mehta
>            Assignee: Karan Mehta
>
> Currently the {{ScanResponse}} proto sends out 1 bit per {{Result}} that it 
> has embeds inside the {{CellScanner}} to indicate if it is partial or not. 
> {code}
>     // In every RPC response there should be at most a single partial result. 
> Furthermore, if
>     // there is a partial result, it is guaranteed to be in the last position 
> of the array.
> {code}
> According to client, only the last result can be partial, thus this repeated 
> bool can be converted to a bool, thus reducing overhead of serialization and 
> deserialization of the array. This will break wire compatibility therefore 
> this is something to look for in upcoming versions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to