[HBASE-26537] FuzzyRowFilter backwards compatibility

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.13, 1.2.12, 1.3.6
• Fix Version/s: 2.5.0, 1.7.2
• Hadoop Flags: Reviewed

Release Note

HBASE-15676 introduced a backwards incompatible change which makes it impossible to upgrade server first, then client, without potentially incorrect scanning results if FuzzyRowFilter is in use. This change corrects that problem by introducing a backwards compatible workaround.

• Assignee: Bryan Beaudreault
• Reporter: Bryan Beaudreault
• Created: 03/Dec/21 15:06
• Updated: 01/Sep/22 10:57
• Resolved: 18/Dec/21 02:56

Description

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. 

Issue Links

• links to: GitHub Pull Request #3916
• links to: GitHub Pull Request #3931

Sub-Tasks

• Cherry pick HBASE-26537 to branch-2.4: Resolved