Add Yardstick upstream parity CI#187
Merged
Merged
Conversation
nicosuave
force-pushed
the
yardstick-upstream-parity
branch
from
b5b530c to
676d0e6
Compare
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
1 participant
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.
Adds a live upstream Yardstick parity workflow that fetches sidequery/yardstick and replays SQL tests without vendoring upstream fixtures.
Extends the Yardstick replay harness to validate both query result blocks and CREATE VIEW ... AS MEASURE model/dimension/metric definitions. The current upstream replay covers 2 SQL files, 273 query blocks, and 86 definition blocks.
Also tightens Yardstick query compatibility around optional semantic prefixes, CTAS/INSERT rewrites, aggregate detection, and ORDER BY alias handling.