[core] Support reading sequence_number in AuditLogTable and BinlogTable #6858
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
This PR adds support for accessing system fields (specifically
sequence_number) inAuditLogTableandBinlogTable.Currently, downstream consumers often need the
sequence_numberto ensure strict ordering or to implement exactly-once processing when reading from audit logs or binlogs. However, these system tables previously did not expose this field.This change implements
KeyValueSystemFieldsRecordReaderto enable the projection of system fields for KeyValue records, allowing users to querysequence_numberdirectly from audit log and binlog tables.Tests
IncrementalReadSystemFieldsTestto verify functionality.AuditLogTableTestandBinlogTableTestto coversequence_numberread cases.API and Format
Documentation