Bugfix 1683: Add validate_index arg to staged data finalization in both V1 and V2 APIs #1694
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.
Reference Issues/PRs
Fixes #1683
What does this implement or fix?
V2 API
finalize_staged_data
continues to validate that index values are sorted and non-overlapping by default, but now checking can be disabled by passingvalidate_index=False
in line with other writing methods.V1 API
compact_incomplete
now allows unsorted timeseries index data by default, and checking can be enabled by passingvalidate_index=True
in line with other writing methods.Also means that when writing incomplete segments, the
validate_index
argument is used to check sortedness or not, previously it was assumed that incompletes had to beASCENDING
.