-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HUDI-8726] s3/gcs incremental source should stick to checkpoint v1 #12688
Open
Davis-Zhang-Onehouse
wants to merge
9
commits into
apache:master
Choose a base branch
from
Davis-Zhang-Onehouse:HUDI-8726-s3gcs
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[HUDI-8726] s3/gcs incremental source should stick to checkpoint v1 #12688
Davis-Zhang-Onehouse
wants to merge
9
commits into
apache:master
from
Davis-Zhang-Onehouse:HUDI-8726-s3gcs
+1,631
−328
Conversation
This file contains 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
Davis-Zhang-Onehouse
force-pushed
the
HUDI-8726-s3gcs
branch
from
January 23, 2025 03:06
75369c9
to
65a87a7
Compare
github-actions
bot
added
size:XL
PR with lines of changes > 1000
and removed
size:M
PR with lines of changes in (100, 300]
labels
Jan 23, 2025
Davis-Zhang-Onehouse
force-pushed
the
HUDI-8726-s3gcs
branch
6 times, most recently
from
January 23, 2025 23:24
33e010e
to
4fc962e
Compare
nsivabalan
reviewed
Jan 24, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Source code changes looks good to me.
while I review test code, reminding @yihua to review the logic and certify
Davis-Zhang-Onehouse
force-pushed
the
HUDI-8726-s3gcs
branch
from
January 25, 2025 17:00
4fc962e
to
7c6952a
Compare
Pure refactoring of the test classes - moving some method to the parent class so the subsequent commits can use them. Extracting methods to a new class so it can be consumed by later changes.
For testing ingestion flow e2e to ensure we consume the right checkpoint version and write out the right checkpoint version, we split the coverage into 2 parts: - Test anything interacting with S3/GCS incremental source. This is done by introducing a dummy class as an injected dependency so we can do validations and trigger the ingestion code covering the e2e behavior - Test S3/GCS incremental source itself, this is done by existing unit test against the class, they have done the testing already about the relevant code part.
Davis-Zhang-Onehouse
force-pushed
the
HUDI-8726-s3gcs
branch
3 times, most recently
from
January 27, 2025 01:21
0c644d8
to
00653bc
Compare
Previously in order for EMPTY_ROW_SET_NONE_NULL_CKP to return different value, we create different BiFunction with hard coded value. Now it is parameterized via RETURN_CHECKPOINT_KEY. Also moved some constant member to the right util class.
Davis-Zhang-Onehouse
force-pushed
the
HUDI-8726-s3gcs
branch
from
January 27, 2025 01:47
00653bc
to
0d26d85
Compare
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.
Reviewers please review commit by commit, checking the commit messages would save you great amount of time
Change Logs
Fixed and bump up massive test coverage for checkpoint and some missing coverage when related code is introduced
How the checkpoint is consumed
How it is produced (from the deepest call stack to the caller at a higher level)
Impact
as title mentioned
Risk level (write none, low medium or high below)
low
Documentation Update
none
Contributor's checklist
Apart from basic unit test, we need e2e functional test of the s3 / gcs source. I can only think of writing IT test coverage.