JanKaul commented on issue #3777: URL: https://github.com/apache/arrow-datafusion/issues/3777#issuecomment-1316582955
> Does it make sense to make the interface async at both the `CatalogProvider` and `SchemaProvider` level? I haven't really looked through the concrete use cases but it seems like we could make `SchemaProvider` async but still have `CatalogProvider` be sync. If a particular implementation needed to prefetch metadata (meta-metadata?) then that could be something handled at construction for that implementation. That's also a good point. I guess this would work for most use cases. On the other hand I think the biggest burden is to change the public interface of datafusion and update the dependencies. If the dependiencies have to be updated due to changes in `SchemaProvider`, I think also updating the interface for `CatalogProvider` is just a minor issue. And one avoids a potential breaking change in the future, in case there are use cases for an async `CatalogProvider`. Overall, I think having an async interface is a cleaner solution. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
