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-1988] FinalizeWrite() been executed twice in AbstractHoodieWrit… #3050
Conversation
…eClient$commitstats
Codecov Report
@@ Coverage Diff @@
## master #3050 +/- ##
============================================
- Coverage 55.31% 54.99% -0.33%
- Complexity 4026 4044 +18
============================================
Files 520 526 +6
Lines 25295 25668 +373
Branches 2872 2950 +78
============================================
+ Hits 13993 14117 +124
- Misses 9914 10164 +250
+ Partials 1388 1387 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@n3nash : can you take this up. I see you have added one of the finalize as part of multi-writer. not sure if it was moved from elsewhere. |
@swuferhong Thanks for opening this. Looks like it might be a duplicate. Can you check why the CI is failing ? |
Yes, we reopened this PR, and CLI passing now. |
@n3nash Thanks, we reopened this PR, and CLI passing now. |
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.
LGTM
…eClient$commitstats
Tips
What is the purpose of the pull request
FinalizeWrite() been executed twice in AbstractHoodieWriteClient$commitstats. once in commitstats() self, another in commit() method in commitstats(). I think this is a useless repetition.
Brief change log
(for example:)
Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Committer checklist
Has a corresponding JIRA in PR title & commit
Commit message is descriptive of the change
CI is green
Necessary doc changes done or have another open PR
For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.