You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2013/06/22 00:54:20 UTC

[jira] [Comment Edited] (HBASE-8401) Backport "HBASE-8284 Allow String Offset(s) in ColumnPaginationFilter for bookmark based pagination"

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

Lars Hofhansl edited comment on HBASE-8401 at 6/21/13 10:53 PM:
----------------------------------------------------------------

I think in case 1 it would leave unread stuff on the wire that would confuse the next reader; in case 2 you'd get an end-of-stream type of exception.

A subclass is OK, because it does not change the existing filter class, so only if somebody used the new class before fully upgrading the cluster (and client) would there be a problem.

                
      was (Author: lhofhansl):
    I think in case 1 it would leave unread stuff on the wire that would confuse the next reader; in case you'd get an end-of-stream type of exception.

A subclass is OK, because it does not change the existing filter class, so only if somebody used the new class before fully upgrading the cluster (and client) would there be a problem.

                  
> Backport "HBASE-8284 Allow String Offset(s) in ColumnPaginationFilter for bookmark based pagination"
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8401
>                 URL: https://issues.apache.org/jira/browse/HBASE-8401
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Varun Sharma
>
> This issue is for discussion of whether or not backport HBASE-8284.  It has been applied to trunk and 0.95.  A patch for 0.94 is over on hbase-8284

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira