returnString commented on issue #1836:
URL:
https://github.com/apache/arrow-datafusion/issues/1836#issuecomment-1041417998
Yeah, my intent when adding the catalog/schema abstractions initially was to
support exactly this use case 😊 You can compose an execution context with any
crazy combination of catalog/schema providers (e.g. @alamb built a wrapper
catalog that automatically builds an `information_schema` based on your _real_
catalog) which can then provide arbitrary `TableProvider` instances for actual
planning/execution work.
I think using this as a common interface for contrib projects (rather than
say building execution contexts directly) would allow for maximum flexibility;
for example, I might want to build a queryable context like:
```
my_warehouse_project (catalog):
raw (objstore provider):
- events (objstore table)
derived (in-mem schema provider):
- daily_event_counts (memtable)
```
--
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]
