[
https://issues.apache.org/jira/browse/HUDI-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Y Ethan Guo updated HUDI-8331:
------------------------------
Sprint: Hudi 1.0 P0s (Pre Code Freeze) (was: Hudi 1.0 Blockers+Bugs Sprint)
> Remove excessive table validity check
> -------------------------------------
>
> Key: HUDI-8331
> URL: https://issues.apache.org/jira/browse/HUDI-8331
> Project: Apache Hudi
> Issue Type: Bug
> Reporter: Shawn Chang
> Assignee: Shawn Chang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.0.0, 0.15.1
>
>
> When initializing HoodieMetaClient and FileSystemBackedTableMetadata, Hudi
> calls this method to check if table has a valid meta path:
> https://github.com/apache/hudi/blob/33a02987b7fc385253dc0e0efbf112066b8cf190/hudi-common/src/main/java/org/apache/hudi/exception/TableNotFoundException.java#L47
> However, this is excessive because Hudi should just fail later on if this
> path is not valid/does not exist. This check is also problematic because it
> adds excessive FS calls, which can be very expensive on S3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
