[HUDI-4142] [RFC-54] New Table APIs and streamline Hudi configs
What is the purpose of the pull request
RFC for new table APIs and config changes.
Brief change log
(for example:)
- Modify AnnotationLocation checkstyle rule in checkstyle.xml
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:)
- Added integration tests for end-to-end.
- Added HoodieClientWriteTest to verify the change.
- Manually verified the change by running a job locally.
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.
cc @xushiyan @fengjian428 I can make you co-author of thir RFC and include your hive sync proposals in this or if you have a draft RFC let me know, i can link that later in this RFC.
cc @xushiyan @fengjian428 I can make you co-author of thir RFC and include your hive sync proposals in this or if you have a draft RFC let me know, i can link that later in this RFC. HI @codope here is RFC 55
CI report:
- 0199defd24d52e00c7dca45e100898911ff778fb Azure: SUCCESS
Bot commands
@hudi-bot supports the following commands:-
@hudi-bot run azurere-run the last Azure build
Does hudi have plan to implement its own efficient data structure like Spark internal row and Flink row data ?
Closing due to inactivity