[spark] Fix RowTrackingTable reading by add _ROW_ID existing check before adding _ROW_ID#7606
Merged
JingsongLi merged 3 commits intoapache:masterfrom Apr 9, 2026
Merged
Conversation
dffb3a1 to
1fc1bae
Compare
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1fc1bae to
9d771a4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
When querying the
$row_trackingsystem table with filters,IllegalArgumentException: Row tracking field name '_ROW_ID' conflicts with existing field namesis thrown. Spark silently catches this exception and falls back to post-scan filtering,
so query results are correct but predicates are not pushed down.
Tests
Row Tracking: query row_tracking system table with filter pushdown