-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
base: master
Are you sure you want to change the base?
[HUDI-8666] Revisit error message when timeline layout version cannot be read #12867
Conversation
519ef99
to
805082f
Compare
16daa7a
to
1371817
Compare
@hudi-bot run azure |
6ded773
to
7b8b533
Compare
7b8b533
to
b9f29f5
Compare
@hudi-bot run azure |
@@ -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) { |
There was a problem hiding this comment.
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.
Change Logs
Changed exception class from
TableNotFoundException
toInvalidTableException
, made error message ofInvalidTableException
more detailed.Impact
Exception type and error message are accurate.
Risk level (write none, low medium or high below)
none
Documentation Update
none
ticket number here and follow the instruction to make
changes to the website.
Contributor's checklist