Epic: Implement remaining `information_schema` tables
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
### Is your feature request related to a problem or challenge?
@JanKaul reported in [Discord](https://discord.com/channels/885562378132000778/1166447479609376850/1197812043969986620):
> Hey all, I'm trying to use Datafusion with Apache Superset. Superset tries to fetch all available schemas using "information_schema.schemata". I realized that the "schemata" table is currently not implemented.
In general many BI and other tools with use the `information_schema` tables to determine the contents of a database. It would be nice to make DataFusion implementations more compatible with the ecosystem at large by implementing more of these tables
### Describe the solution you'd like
It would be nice to implement more of the information_schema for DataFusion to increase the compatibility
There are many, many tables defined in the `information_schema` (see [postgres docs](https://www.postgresql.org/docs/current/information-schema.html) , many of them potentially impossible to implement in DataFusion (e.g. `administrable_role_authorizations`
## Tasks
- [x] #8917
Contributor guide
Research direction
Start by reviewing the completed task #8917 and the PostgreSQL information_schema documentation linked in the issue. Inventory the remaining tables that DataFusion can support, then define the implementation scope and validation needed for broader ecosystem compatibility. Done means the selected remaining tables are implemented and their compatibility is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100