feat(schema-compiler): Allow to specify td with granularity in REST API query order section #9630
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.
This PR introduces the ability to specify granularity in the order section of the query and fixes the ordering when same time dimension is requested multiple times (with different granularities).
Imaging you have a query like this:
Note the
order
part.Before now - the sorting will be done by 1st td with
month
granularity. But resulting rows still could jump around because week timestamps inside one month are not guaranteed to be ordered. Now column with the lowest granularity (week in the example) will be used for ordering.Btw, this also works with custom granularities! ;)
To have full control, now you can specify the
granularity
in the order section like this:or like this:
Check List