Repository navigation
series: sort points by full timestamp, not whole seconds - #3
Merged
Merged
Conversation
Sorting on timestamp() collapsed points within the same second, so sub-second inputs kept their input order. Sort on the DateTime itself, matching align/timeline/correlate which already keep sub-second precision. Display stays at second resolution.
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
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.
Summary
ts-seriespoints by the fullDateTimeinstead oftimestamp()(whole seconds), so points within the same second follow time order rather than input order.ts-serieswithts-align,ts-timelineandts-correlate, which already keep sub-second precision. Output format is unchanged (rows still print at second resolution).attime now points to the earlier one.sorts_within_the_same_second.Verification
.900then.100within one second prints values 1 → 9.