-
Notifications
You must be signed in to change notification settings - Fork 114
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
Added minimum for search.cancel_after_time_interval setting for rollups #1026
Changes from 5 commits
d98fd53
166c303
687c7e7
a259d1c
a37c248
24a578d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,6 +20,7 @@ class RollupSettings { | |
const val DEFAULT_RENEW_LOCK_RETRY_DELAY = 1000L | ||
const val DEFAULT_CLIENT_REQUEST_RETRY_COUNT = 3 | ||
const val DEFAULT_CLIENT_REQUEST_RETRY_DELAY = 1000L | ||
const val MINIMUM_CANCEL_AFTER_TIME_INTERVAL_MINUTES = 10L | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. could this be a ISM specific cluster settings and default value is 10 minutes? @bowenlan-amzn WDYT? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, it will be more flexible. @Joshua152 can do this as a follow up. |
||
|
||
val ROLLUP_ENABLED: Setting<Boolean> = Setting.boolSetting( | ||
"plugins.rollup.enabled", | ||
|
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.
can add a unit test for code coverage CI