[HUDI-1328] Introduce HoodieFlinkEngineContext to hudi-flink-client#2161
[HUDI-1328] Introduce HoodieFlinkEngineContext to hudi-flink-client#2161leesf merged 1 commit intoapache:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2161 +/- ##
=========================================
Coverage 53.61% 53.61%
Complexity 2845 2845
=========================================
Files 359 359
Lines 16535 16535
Branches 1777 1777
=========================================
Hits 8866 8866
Misses 6912 6912
Partials 757 757
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
use HoodieException?
done
There was a problem hiding this comment.
maybe we would move the methods to super class as default implementation after finishing the flink integration.
There was a problem hiding this comment.
maybe we would move the methods to super class as default implementation after finishing the flink integration.
Good idea
There was a problem hiding this comment.
here would always get spark instead of flink?
There was a problem hiding this comment.
here would always get
sparkinstead offlink?
It should be. List is ordered.
Assertions.assertNotNull(resultMap.get("hudi")) should be better understood
9a244af to
be70afd
Compare
vinothchandar
left a comment
There was a problem hiding this comment.
I am okay with the PR as-is. IIUC this change does not really add any flink related changes. It might be good to have PRs, such that add some functionality in each PR.
Also +1 on deferring further refactoring/reorganization until we can implement a first cut of flink support.
Yes, this PR actually aims to introduce |
|
sg! @wangxianghu I ll let @leesf or @yanghua do the merging once they are ready |
Merging this PR. cc @vinothchandar |
Tips
What is the purpose of the pull request
Introduce HoodieFlinkEngineContext to hudi-flink-client
Brief change log
(for example:)
Verify this pull request
This pull request is already covered by existing tests, such as TestHoodieFlinkEngineContext.
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.