Bug fix: CLI saved queries dropping order_by_names
param
#835
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.
Description
Bug fix. In the CLI, we are using the
MetricFlowQueryRequest.order_by_names
param. When passing that query to the query parser, we end up dropping that param in favor of order by objects, instead. This meant the order by param was dropped entirely from CLI saved queries, returning unexpected results. You can see one of the hardcoded result sets has the incorrect order. This PR makes sure both get passed through to the final query, fixing the ordering issue.