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

[HUDI-8666] Revisit error message when timeline layout version cannot be read #12867

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

wombatu-kun
Copy link
Contributor

@wombatu-kun wombatu-kun commented Feb 21, 2025

Change Logs

Changed exception class from TableNotFoundException to InvalidTableException, made error message of InvalidTableException more detailed.

Impact

Exception type and error message are accurate.

Risk level (write none, low medium or high below)

none

Documentation Update

none

  • The config description must be updated if new configs are added or the default value of the configs are changed
  • Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
    ticket number here and follow the instruction to make
    changes to the website.

Contributor's checklist

  • Read through contributor's guide
  • Change Logs and Impact were stated clearly
  • Adequate tests were added if applicable
  • CI passed

@wombatu-kun wombatu-kun force-pushed the HUDI-8666_invalid_table_exception branch from 519ef99 to 805082f Compare February 21, 2025 05:40
@github-actions github-actions bot added the size:S PR with lines of changes in (10, 100] label Feb 21, 2025
@wombatu-kun wombatu-kun force-pushed the HUDI-8666_invalid_table_exception branch 2 times, most recently from 16daa7a to 1371817 Compare February 21, 2025 06:54
@wombatu-kun
Copy link
Contributor Author

@hudi-bot run azure

@wombatu-kun wombatu-kun marked this pull request as draft February 21, 2025 14:55
@wombatu-kun wombatu-kun force-pushed the HUDI-8666_invalid_table_exception branch 2 times, most recently from 6ded773 to 7b8b533 Compare February 21, 2025 15:24
@wombatu-kun wombatu-kun force-pushed the HUDI-8666_invalid_table_exception branch from 7b8b533 to b9f29f5 Compare February 21, 2025 15:31
@wombatu-kun
Copy link
Contributor Author

@hudi-bot run azure

@wombatu-kun wombatu-kun marked this pull request as ready for review February 22, 2025 01:43
@hudi-bot
Copy link

CI report:

Bot commands @hudi-bot supports the following commands:
  • @hudi-bot run azure re-run the last Azure build

@@ -149,7 +150,7 @@ public String createTable(
try {
HoodieTableMetaClient.builder().setConf(HoodieCLI.conf.newInstance()).setBasePath(path).build();
existing = true;
} catch (TableNotFoundException dfe) {
} catch (TableNotFoundException | InvalidTableException dfe) {
Copy link
Contributor

Choose a reason for hiding this comment

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

The checked exception is hard to maintain in code, you don't expect developer to catch 2 checked exceptions every time initialing the meta client, no one can follow the rules. How about we just strengthen the error msgs first for the timeline layout.

As for the exception throwing, maybe we should switch to RuntimeException instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:S PR with lines of changes in (10, 100]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants