-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TSDB: fix reindex failed tests without feature flag #81967
Conversation
Pinging @elastic/es-analytics-geo (Team:Analytics) |
@elasticmachine test this please |
Lgtm
…On Mon, Dec 20, 2021, 11:52 PM Igor Motov ***@***.***> wrote:
@elasticmachine <https://github.com/elasticmachine> test this please
—
Reply to this email directly, view it on GitHub
<#81967 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABUXISGIZBP5IFHHBKMKSTUSABZLANCNFSM5KPC4QCQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are on a team that was mentioned.Message
ID: ***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes in gradle fix the issue I don't think change in TimestampBounds are necessary.
scopedSettings.addSettingsUpdateConsumer(IndexSettings.TIME_SERIES_END_TIME, this::updateEndTime); | ||
if (IndexSettings.isTimeSeriesModeEnabled()) { | ||
scopedSettings.addSettingsUpdateConsumer(IndexSettings.TIME_SERIES_END_TIME, this::updateEndTime); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why this is necessary. It seems like TimestampBounds instantiation is already guarded by check for the TIME_SERIES_START_TIME
in
this.timestampBounds = TIME_SERIES_START_TIME.exists(settings) ? new TimestampBounds(scopedSettings) : null; |
I think @nik9000 had to add this check in #80945 because there was no protection there.
So
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But I've been known to be wrong about things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a note about the change in the java file.
@elasticmachine update branch |
@elasticmachine test this please |
@mark-vieira my apologizes, will not happen again. I am on it. |
No worries. Stuff gets lost in the shuffle over the holidays. Thanks, Igor! |
@elasticmachine test this please |
@elasticmachine test this please |
@elasticmachine run elasticsearch-ci/release-tests |
@elasticmachine run elasticsearch-ci/release-tests |
1 similar comment
@elasticmachine run elasticsearch-ci/release-tests |
@elasticmachine run elasticsearch-ci/release-tests |
@elasticmachine test this please |
@elasticmachine run elasticsearch-ci/release-tests |
@elasticmachine update branch |
there is another failed test, cause the release check failed:
|
@elasticmachine, test this please. |
I've removed the test-release flag from this PR. I'll look into that failure and open a follow up PR to fix the release tests. It's nice to have the bot's full trust for fixing that because the build will fail over and over and over and over again.... |
Removing it doesn't stop the tests! Nice. Oh well. I have to do a thing for a bit. I'll look again soon.... |
This error isn't ours!
I'm going to merge this and ping the ml folks with this error. |
I reproduced with:
|
fix as the elastic#80945 do. register a settings update consumer for the end_time for the tsdb index even when the end_time setting wasn't registered. Pass the feature flag to reindex yaml tests. Co-authored-by: Igor Motov <[email protected]>
fix as the elastic#80945 do. register a settings update consumer for the end_time for the tsdb index even when the end_time setting wasn't registered. Pass the feature flag to reindex yaml tests. Co-authored-by: Igor Motov <[email protected]>
fix as the #80945 do.
register a settings update consumer for the end_time for
the tsdb index even when the end_time setting wasn't registered.
Pass the feature flag to reindex yaml tests.