[Connectors] Add golden table for row tracking tests #4924
Closed
Conversation
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
Signed-off-by: Lennart Behme <[email protected]>
lbhm
force-pushed
the
golden-table-row-tracking
branch
from
ec42893 to
9dfb60d
Compare
5 tasks
johanl-db
approved these changes
Jul 17, 2025
|
Please just define the test in-line for Kernel! Sorry that this wasn't clearly documented |
|
I see, closing this PR then. |
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.
Which Delta project/connector is this regarding?
Description
This PR adds a golden table with row tracking enabled as a resource for testing the row tracking reader in Delta kernel (to be implemented soon).
To verify whether Delta kernel can correctly read a table with row tracking that was created by Delta Spark, I create a small dummy table and then run a
MERGEop that updates a value and inserts a new value so that we have all combinations of materialized/not-materialized row IDs and row commit versions.How was this patch tested?
This PR adds new resources/reference solutions for future tests.
Does this PR introduce any user-facing changes?
No