-
Notifications
You must be signed in to change notification settings - Fork 178
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
[ADAP-547] [Feature] Pagination to allow >10k schemas per database #605
Comments
Thanks for opening this @jaypeedevlin ! ✅ Green light for you to use the same technique as #572 but applied to >10k schemas. In a ideal world, you will be able to refactor The crux would be generalizing the Ultimately, that will be up to you and the code reviewer to work out. |
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Bump |
Hello, are there any updates for this or any new related issues? |
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers. |
Is this your first time submitting a feature request?
Describe the feature
#571 used pagination to support retrieving >10k objects in a schema. The same pattern can be used to enable >10k schemas in a database.
I propose to use the same technique for the latter as the former (which I've confirmed Snowflake supports).
Describe alternatives you've considered
Overriding the macro in our project.
Who will this benefit?
Anyone using dbt at scale — specifically we run into this from time to time with our databases that create an environment per PR for dev.
Are you interested in contributing this feature?
Yes!
Anything else?
No response
The text was updated successfully, but these errors were encountered: