-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Specifying the timeout for the _msearch in the body #26446
Conversation
@jasontedor when you determine whether or not this was supported, but deprecated in 6.x, would you mind letting us know so we know how far to backport this? |
💔 Build Failed |
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.
LGTM, code review only.
💔 Build Failed |
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.
👍
This use of |
* Specifying the timeout for the msearch in the body * Revert "Specifying the timeout for the msearch in the body" This reverts commit 7b07bfa. * Fixing the courier and the index pattern execute script timeouts
* Specifying the timeout for the msearch in the body * Revert "Specifying the timeout for the msearch in the body" This reverts commit 7b07bfa. * Fixing the courier and the index pattern execute script timeouts
💔 Build Failed |
The
_msearch
API in ES master is returning a 400/bad-request when specifying the timeout in the header without units. This PR moves this parameter to the search body.At this moment, it's unknown how far this should be backported... it's possible that the parameter that we're specifying in the header on 6.x (and potentially earlier) is simply being ignored.
"Release Note: Resolving issue with the _msearch timeouts being specified incorrectly, which was causing them to be ignored."