Should IcebergCatalogProvider::try_new
not short-circuit on the first failed IcebergSchemaProvider::try_new
?
#1651
krishnakeshan
started this conversation in
General
Replies: 1 comment
-
I have concerns about this change, which makes the error hidden from user. I think a more reasonable approach is to load schema/table lazily, e.g. only load them when necessary, and reports the error when loading a corrupted schema/table. But due to the limitation of datafusion's trait definition, we can't do it for now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been working with a GCS bucket that has some invalid schemas that cause
IcebergSchemaProvider::try_new
to fail. When building these schemas withIcebergCatalogProvider::try_new
, I'm unable to get the catalog provider for valid schemas due to some corrupted schemas. I modified the method like below and it works fine for me:I'm not mentioning the error currently as my question is about whether such a method makes sense. I can add error details if those would help make a decision
Beta Was this translation helpful? Give feedback.
All reactions