Correct way to `register_listing_table` on specific catalog / schema?
- 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?
Problem; I have 2 schemas in one catalog. `datafusion.public` (default) and `datafusion.archive` (secondary). I want to put some tables in one schema and the rest of the other. But it doesnt seems that it's possible to pass an option or modify the state of the context.
### Describe the solution you'd like
No idea, but maybe `ctx.set_catalog(String)` or `ctx.set_schema(String)`
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by locating register_listing_table and the context handling for catalogs and schemas. Determine how registrations are currently assigned to datafusion.public, then define and verify a way to place tables in datafusion.public or datafusion.archive independently; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100