[jira] [Comment Edited] (HBASE-26537) FuzzyRowFilter backwards compatibility

["Andrew Kyle Purtell (Jira)" <ji...@apache.org>]

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

Andrew Kyle Purtell edited comment on HBASE-26537 at 12/9/21, 7:56 PM:
-----------------------------------------------------------------------

HBASE-15676 was committed to 1.2.2. Would it have been possible to solve this by upgrading from 1.2.0 to 1.2.2 or later 1.2.x i.e if you had kept up to date with the patch releases of the version you were on there would have been no issue? Shouldn't that be the recommended path?


was (Author: apurtell):
HBASE-15676 was committed to 1.2.2. Would it have been possible to solve this by upgrading from 1.2.0 to 1.2.2 or later? Shouldn't that be the recommended path?

> FuzzyRowFilter backwards compatibility
> --------------------------------------
>
>                 Key: HBASE-26537
>                 URL: https://issues.apache.org/jira/browse/HBASE-26537
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.13, 1.2.12, 1.3.6
>            Reporter: Bryan Beaudreault
>            Priority: Major
>
> HBASE-15676 introduced a backwards incompatible change which makes it impossible to upgrade in our designated upgraded order (server first, then client) without potential bad results. Worse, the failure mode is silent – a pre-HBASE-15676 client would incorrectly receive 0 results from a post-HBASE-15676 server.
> I solved this internally as part of our upgrade from 1.2.0 to 2.4.6 by adding a new proto field to switch between the two implementations. I'm submitting this Jira to capture and potentially backport that fix for anyone else who encounters it. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)