fix(query): drop emptyCube.emptyKey order placeholder before sending#38
Merged
Conversation
The query builder emits `emptyCube.emptyKey` as a "no order selected"
sentinel in the order state. normalizeOrders passed it straight into the
Cube query as `order: {"emptyCube.emptyKey":"asc"}`. The legacy Cube
planner silently ignored the unresolvable member; the Tesseract planner
rejects it ("Cannot resolve: emptyCube") and 500s the query. Filter the
placeholder out in normalizeOrders (both the REST-API and export paths).
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.
The query builder emits
emptyCube.emptyKeyas a "no order" sentinel;normalizeOrdersforwarded it asorder: {"emptyCube.emptyKey":"asc"}. Legacy Cube ignored it; the Tesseract planner rejects it (Cannot resolve: emptyCube) → 500. Filters the placeholder in bothnormalizeOrderscopies (REST-API + export). Pairs with the backend guard in synmetrix#63.