This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Fix exception with Instant type when performing continuous rollup #373
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.
Issue #, if available: #364
Description of changes:
Passing in
Instant
to theRangeQueryBuilder
when creating search requests for continuous rollups leads tocan not write type [class java.time.Instant]
exceptions. Converting Instant to epoch millis as Long to fix this issue.The problem was reproduced locally and confirmed that this change fixed continuous rollups and the target index contents were validated against the source index for consistency.
Some tests specifically validating continuous rollup output or search consistency should be added. If they aren't addressed here, they will be tracked as a follow-up item.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.