[AMORO-2861]: Support display Hudi table metadata in Amoro Dashboard
Why are the changes needed?
Close #2861.
Brief change log
- Add hudi table catalog support
- Implement hudi format catalog for Hadoop metastore.
- Implement hudi format catalog for Hive metastore
How was this patch tested?
-
[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible
-
[ ] Add screenshots for manual tests if appropriate
-
[ ] Run test locally before making a pull request
Documentation
- Does this pull request introduce a new feature? (yes / no)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
Support choose Hudi format when create hive/hadoop catalog.
Support display Hudi tables in catalog, with hudi icon.
Table details
Support display Hudi table details, include table summary, scheme, metrics, table type and properties
Support display partitions and files in partitions.
Due to limit of hudi api, some field without values.
Support display timeline as snapshots
Due to limit of hudi api, records statistic is missed, and file count is incorrect for deltacommit.
Support display compact/cluster instant as optimizing process
Only show completed instant, and show compact as minor optimize, cluster as major optimize.
DDL
Due to limit of hudi api, DDL history is empty.
Some check style errors exist, which you may want to fix. @baiyangtx
cc @majin1102 @zhoujinsong
when use getTableSnaphots, some exception occurs.
Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'Objavro': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') as [Source: (String)"Obj\u0001\u0002\u00016avro.schema\u0015{"type":"record","name":"HoodieCleanMetadata", ......}]
when use snapshot detail ,the exception is Getting all partition paths with file system listing sequentially can be very slow. This should not be invoked.
when use snapshot detail ,the exception is Getting all partition paths with file system listing sequentially can be very slow. This should not be invoked.
@yhf20071 Thanks for the feedback.
Can you create GH issues to help the community track these bugs?