Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(descheming): add catalog kwarg to table accessing methods #9000

Open
Tracked by #9638
gforsyth opened this issue Apr 18, 2024 · 2 comments
Open
Tracked by #9638

feat(descheming): add catalog kwarg to table accessing methods #9000

gforsyth opened this issue Apr 18, 2024 · 2 comments
Labels
breaking change Changes that introduce an API break at any level feature Features or general enhancements

Comments

@gforsyth
Copy link
Member

In #8655 we deprecated the non-hierarchical usage of schema everywhere (hopefully).

In an effort to make that as smooth as possible for users, we settled on a pattern of allowing passing in either a tuple of strings or a dotted string path "catalog.database" as the argument to the database kwarg.

Once schema is removed, we should also add a catalog kwarg to allow users to specify table hierarchy in a slightly more programmatic way. There is some bookkeeping around how to handle combinations of arguments to catalog and database, but we've effectively already written it all, just for database and schema.

xref 8867

@ncclementi
Copy link
Contributor

@gforsyth quick question, schema gets removed in 10.0. I'm assuming that this one should be tackled only after that release correct?

@gforsyth
Copy link
Member Author

we could add it in the same release, or in 10.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Changes that introduce an API break at any level feature Features or general enhancements
Projects
Status: backlog
Development

No branches or pull requests

2 participants