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.

Sign up for GitHub

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

Jump to bottom

Improve the performance of the at_least_one test by pruning early. #775

Closed
JoshuaHuntley opened this issue Mar 29, 2023 · 0 comments · Fixed by #776
Closed

Improve the performance of the at_least_one test by pruning early. #775

JoshuaHuntley opened this issue Mar 29, 2023 · 0 comments · Fixed by #776
Labels
enhancement New feature or request triage

Comments

@JoshuaHuntley
Copy link
Contributor

JoshuaHuntley commented Mar 29, 2023 •
edited
Loading

Describe the feature

I would like the at_least_one test to return values faster. In some applications it is very slow.

Describe alternatives you've considered

Not using the test.

Additional context

I believe that the new feature can be added to the SQL code in a way that is compatible with any standard SQL database.

Who will this benefit?

Any user with large tables or external (slow) data sources or tables.

Are you interested in contributing this feature?

Yes, I've already done the update and will file a PR shortly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Improve the performance of the at_least_one test JoshuaHuntley/dbt-utils
1 participant
@JoshuaHuntley