Repository navigation
fix(thoughtspot): portable expressions — unqualify a field's, quote what needs quoting #463
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
Merged
jbonofre
merged 7 commits into
apache:main
from
djwaldo:fix/thoughtspot-metric-portability
Oct 6, 2026
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
89e7af0
fix(thoughtspot): a field's portable expression must not be dataset-q…
djwaldo 4fa2ea8
fix(thoughtspot): quote a portable identifier that is not a regular one
djwaldo 9d9feee
fix(thoughtspot): preserve an explicit `aggregation: NONE` across a r…
djwaldo ead5cac
fix(thoughtspot): an absent aggregation is ThoughtSpot's default, SUM…
djwaldo f7de8f5
fix(thoughtspot): a reserved word is not a bare portable identifier
djwaldo 8d8a2a4
test(thoughtspot): run the upstream SQL validation over the fixtures
djwaldo 51b795f
fix(thoughtspot): undouble a quoted identifier on the way back to TML
djwaldo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding
sqlglotto the dev group is a great improvement.As a follow-up in
tests/test_fixtures.py,test_expected_output_validates_against_the_upstream_schemacurrently only validates againstossie-schema.jsonand doesn't run SQL validation. If we also invokedvalidate_sql(orvalidation/validate.py) there whensqlglotis available,pytestwould catch SQL parse errors in fixtures (like thestore.onissue) directly during test runs.