JanKaul commented on issue #3777: URL: https://github.com/apache/arrow-datafusion/issues/3777#issuecomment-1319144722
> 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. After a more detailed look at the source code I would like to come back to your suggestion @thinkharderdev. If we use async traits for `CatalogProvider` and `CatalogListProvider` the `new` constructors of `SessionState` and `SessionContext` will be async. Maybe that was obvious, but I didn't think of it. I would like to get your opinion in which of the following two solutions you prefer: 1. `SchemaProvider`, `CatalogProvider` and `CatalogListProvider` async => `SessionContext::new()` and `SessionState::new()` are async 2. only `SchemaProvider` async => less flexibility with `CatalogProvider` and `CatalogListProvider` -- 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]
