Skip to content
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

[#4952] feat(hudi-catalog): add implementation of HMSBackend for Hudi catalog #4942

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mchades
Copy link
Contributor

@mchades mchades commented Sep 13, 2024

What changes were proposed in this pull request?

support read operations for Hudi catalog HMS backend

Why are the changes needed?

Fix: #4952

Does this PR introduce any user-facing change?

no

How was this patch tested?

UTs added

@mchades mchades changed the title implementation of HMSBackend for Hudi catalog [#4952] feat(hudi-catalog): add implementation of HMSBackend for Hudi catalog Sep 18, 2024
@mchades mchades marked this pull request as ready for review September 18, 2024 06:52
.put(
LOCATION,
PropertyEntry.stringOptionalPropertyEntry(
LOCATION, "The directory for Hudi dataset storage", false, null, false))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we please follow the style to add comment like /* required */ to the input variables.

.put(
LOCATION,
stringImmutablePropertyEntry(
LOCATION, "The location for Hudi table", false, null, false, false))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here.

c ->
c.getTables(schemaIdent.name(), "*").stream()
.map(table -> NameIdentifier.of(namespace, table))
.toArray(NameIdentifier[]::new));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will here list all the tables, not just Hudi table, should we filter out non-hudi table?

Comment on lines +64 to +66
partitioning = HiveTableConverter.getPartitioning(hmsTable);
sortOrders = HiveTableConverter.getSortOrders(hmsTable);
distribution = HiveTableConverter.getDistribution(hmsTable);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does Hudi store such information in HMS, is it compatible with Hive table? As I know, for Iceberg, we need some Iceberg APIs to get partitioning, sortOrders, because Iceberg will store such information in it's metadata file, not in HMS, I guess Hudi is similar, can you please confirm this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Subtask] Support read operations of HMSBackend for Hudi catalog
2 participants