[
https://issues.apache.org/jira/browse/HBASE-26537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456715#comment-17456715
]
Bryan Beaudreault commented on HBASE-26537:
-------------------------------------------
Yea I agree – I wouldn't do it myself, instead I'd go to 2.x. We're in a weird
spot because these affected releases are so old. If you guys think I should
commit this to branch-2 as well, I can give it a shot. It seems a little
unfortunate, but not the end of the world. I think we can all agree to leave it
out of master.
The other thing to note is, I made the most expedient change here, because I
needed to quickly get past this issue and onto other things. There may be a
better way. Unfortunately I can't commit to looking into that in the near
future, but wanted to provide this in case it helped anyone. We could leave
this Jira open for a bit with the attached patch and if I have time in the
future I can try a different, cleaner approach. If someone else wants to take
it over that's also ok.
> 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
>
> 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)
