[
https://issues.apache.org/jira/browse/HBASE-26537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456757#comment-17456757
]
Andrew Kyle Purtell edited comment on HBASE-26537 at 12/9/21, 10:05 PM:
------------------------------------------------------------------------
bq. If you guys think I should commit this to branch-2 as well
I think we do, if the intent is to support server-first upgrade scenarios with
this filter in use. There are going to be other issues and errata going from
older 1.x to 2.5.0+ but this won't be one.
bq. I think we can all agree to leave it out of master.
Agreed. Set fixVersions accordingly.
was (Author: apurtell):
bq. If you guys think I should commit this to branch-2 as well
I think we do, if the intent is to support server-first upgrade scenarios with
this filter in use.
bq. I think we can all agree to leave it out of master.
Agreed. Set fixVersions accordingly.
> 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
> Assignee: Bryan Beaudreault
> Priority: Major
> Fix For: 2.5.0, 1.8.0, 2.6.0
>
>
> 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)
