Repository navigation
fix(config): use the query warehouse for standalone test, scenario and janitor - #942
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Standalone
sqb test,sqb scenarioandsqb janitorwork on fixture data or catalogue metadata, so running them on thebuildwarehouse group pays a large warehouse's minimum resume time for small work (follow-up to CHI-483, before its first release).Changes
test,scenarioandjanitorto thequerywarehouse group.auditandcheckstay inbuildbecause they read real tables and outputs.sqb buildstill use thebuildgroup (one warehouse per invocation).Verification
audit,checkandbuild; existing real-CLI warehouse tests.make test,make check-ci.