remove isDescending from Query interface, move to TimeseriesQuery #16917
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
Follow-up to #16533,
Query.isDescending()
can only be set byTimeseriesQuery
, everything else hard-coded this parameter to the valuefalse
, and it is only used byTimeseriesQuery
to control the direction of time ordering in results.Release note
(for developers)
Query.isDescending
has been moved from the baseQuery
interface toTimeseriesQuery
since it was the only built-in query type which could set or use this parameter. If you have developed a custom query type or query engine extension that utilized this method on theQuery
interface, it will need to be moved to the custom query type, replaced with false if referencing any built-in query type that is not timeseries, or handle the query as aTimeseriesQuery
directly if it is referencing a timeseries query.