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

Lars Hofhansl commented on HBASE-2214:
--------------------------------------

Hi Ferdy, we definitely appreciate all the work you put in for this patch! It 
is still in 0.96. :)  We'll try to find a way to use your patch without 
changing the version number.

The problem with changing the version number (in 0.94 and prior) is that then 
the newer version of the object cannot be deserialized by an older version.
You can see this Scan.readFields(), which throws an exception if it reads a 
version newer than the one it expects.
In practice this means that now a new client cannot issue a scan request to an 
older server, because the server cannot deserialize the scan object.

In 0.96 and later these kind of problems are solved by protobufs.

                
> Do HBASE-1996 -- setting size to return in scan rather than count of rows -- 
> properly
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-2214
>                 URL: https://issues.apache.org/jira/browse/HBASE-2214
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: stack
>             Fix For: 0.96.0, 0.94.2
>
>         Attachments: HBASE-2214-0.94-v2.txt, HBASE-2214-0.94-v3.txt, 
> HBASE-2214-0.94.txt, HBASE-2214-v4.txt, HBASE-2214-v5.txt, HBASE-2214-v6.txt, 
> HBASE-2214-v7.txt, HBASE-2214_with_broken_TestShell.txt
>
>
> The notion that you set size rather than row count specifying how many rows a 
> scanner should return in each cycle was raised over in hbase-1966.  Its a 
> good one making hbase "regular" though the data under it may vary.  
> HBase-1966 was committed but the patch was constrained by the fact that it 
> needed to not change RPC interface.  This issue is about doing hbase-1966 for 
> 0.21 in a clean, unconstrained way.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to