-
Notifications
You must be signed in to change notification settings - Fork 115
Add serverless refresh interval #5323
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
Conversation
|
Following you can find the validation changes against the target branch for the APIs. No changes detected. You can validate these APIs yourself by using the |
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.
Thanks! Regarding backporting, it could go either way, but since it's shared I'd backport. It will also reduce the likelihood of future conflicts.
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.
Thanks! LGTM.
* add serverless refresh interval * rebuild json for adding serverless refresh interval note * no search idle in serverless * regenerate spec (cherry picked from commit bb6d3e7)
* add serverless refresh interval * rebuild json for adding serverless refresh interval note * no search idle in serverless * regenerate spec (cherry picked from commit bb6d3e7)
* add serverless refresh interval * rebuild json for adding serverless refresh interval note * no search idle in serverless * regenerate spec (cherry picked from commit bb6d3e7) Co-authored-by: shainaraskas <[email protected]>
* add serverless refresh interval * rebuild json for adding serverless refresh interval note * no search idle in serverless * regenerate spec (cherry picked from commit bb6d3e7) Co-authored-by: shainaraskas <[email protected]>
The stack and serverless elasticsearch APIs have a different default minimum refresh interval. reflecting this in the API docs for
/{index}/_refreshto reduce confusion.https://bump.sh/preview/5d9553f5-3c52-433b-8b03-84c09359bc57/operation/operation-indices-refresh
@elastic/developer-docs let me know if I'm breaking the rules with my approach / missed something special about adding serverless-specific details.
related to elastic/docs-content#1643
assuming this doesn't need to be backported because it is serverless-only. let me know if that's wrong because it's a shared description