optimize the hoodie hive client and ddl executor code with simpler and clearer abstraction
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
currently. HoodieHiveClient both have DDLExecutor and IMetaStoreClient instance, some ddl executor implemented such as HMSDDLExecutor and HiveQueryDDLExecutor will create IMetaStoreClient instance again. some method in HoodieHiveClient operate HMS both use ddl executor and IMetaStoreClient instance. it look not a clear style. we do some change here.
1.HoodieHiveClient operate HMS only via DDLExecutor instance.
2.Only create IMetaStoreClient instance one time, and pass to ddl executor
3.no need create partitionValueExtractor in HoodieHiveClient, use DDLExecutor's partitionValueExtractor
4.no need public declaration of interface(DDLExecutor) method ,remove it
5.remove some unused import
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-3651
- Type: Improvement
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.