Skip to content

HBASE-29974: Persist filter hints across scan circuit breaks#8464

Open
shubham-roy wants to merge 1 commit into
apache:branch-2.5from
shubham-roy:HBASE-29974-branch-2.5
Open

HBASE-29974: Persist filter hints across scan circuit breaks#8464
shubham-roy wants to merge 1 commit into
apache:branch-2.5from
shubham-roy:HBASE-29974-branch-2.5

Conversation

@shubham-roy

Copy link
Copy Markdown
Contributor

Backport of HBASE-29974 to branch-2.5 (cherry-picked from master 21d3fdf, PR #7882). Adapted for branch-2.5: ExtendedCell → Cell (branch-2.5 predates the ExtendedCell migration), and the nextRowViaHint fast path drops the ScannerContext.setSkippingRow calls (that API — HBASE-27558 — is not on branch-2.5). Tests unchanged (JUnit 5, delete-marker tests retained since HBASE-29039 is present); HBaseTestingUtil → HBaseTestingUtility for the pre-rename branch. No-op by default.

Generated-by: Claude Opus 4.6 (1M context) noreply@anthropic.com
(cherry picked from commit 21d3fdf)

…7882)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Generated-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Signed-off-by: Viraj Jasani <vjasani@apache.org>
(cherry picked from commit 21d3fdf)

@Umeshkumar9414 Umeshkumar9414 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

* as logically stateless. Only filters whose hint computation is based solely on immutable
* configuration (e.g. a fixed column range or a fuzzy-row pattern) should override this.</li>
* <li>The returned {@link Cell}, if non-null, must be an
* {@link org.apache.hadoop.hbase.ExtendedCell} because filters are evaluated on the server

@Umeshkumar9414 Umeshkumar9414 Jul 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this comment related to ExtendedCell still apply ?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's fine to keep for backport PR if master and branch-2 already has this comment. We can update them all later as addendum PR if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants