returnString opened a new pull request #205:
URL: https://github.com/apache/arrow-datafusion/pull/205
# Which issue does this PR close?
Closes #191.
# Rationale for this change
This allows registered TableProviders to approximately indicate the
mechanism used to retrieve data during query execution, which in turn allows
tables to be logged with a `table_type` column in `information_schema.tables`.
This was previously partially supported by classifying all registered tables as
`BASE TABLE` and all generated system tables as `VIEW`.
This means that DataFusion consumers can now build systems that allow
end-users to differentiate between relation types. For example, you could build
a TableProvider that stores a query plan, use this as a view in your execution
context, and end users would be aware that any queries over it in turn trigger
use a query internally.
# What changes are included in this PR?
- Added `TableType` enum
- Exposed new trait method, `TableProvider::table_type`
- Updated information_schema builder to use new table types
# Are there any user-facing changes?
`TableProvider::table_type` is introduced as a new trait method, but comes
with a default implementation returning `TableType::Base` to preserve
back-compact.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
