timsaucer opened a new issue, #1142: URL: https://github.com/apache/datafusion-python/issues/1142
## Background Right now in the python interface the catalog provider is mostly not useful. We have a PR incoming that will change that. The issue I see is that in datafusion core repository we have a naming convention of `catalog/schema/table`. But in the `datafusion-python` repository it's called `catalog/database/table`. I've seen other places use the convention `catalog/namespace/table`. ## User feedback request Should we continue on as we have it or should we try to align on the same naming as in the upstream repo? I ask because right now I bet nearly no users have more than a single database/schema so it is likely not a problem if we update this soon. -- 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: github-unsubscr...@datafusion.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
