-
Notifications
You must be signed in to change notification settings - Fork 81
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
[Integration testing] Remove AltErr and only expect 400 from ES bulk API #4012
[Integration testing] Remove AltErr and only expect 400 from ES bulk API #4012
Conversation
This pull request does not have a backport label. Could you fix it @ycombinator? 🙏
|
|
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.
+1
Looks like we have a failure on
|
This change is already part of this PR. So I'm not sure why this is test is failing. Investigating... |
79e38b1
to
c8486b1
Compare
Quality Gate passedIssues Measures |
Should we backport this to 8.16 also? |
Doesn't look like the ES fix was backported to |
…pect 400 from ES bulk API (#4030) * [Integration testing] Remove AltErr and only expect 400 from ES bulk API (#4012) * Remove AltErr * Fixed error type (cherry picked from commit 1ae9ab6) # Conflicts: # internal/pkg/bulk/bulk_integration_test.go * Update bulk_integration_test.go Fix mergify mess * Printing out filename for debugging * Fixing up conflicts * Trigger Build --------- Co-authored-by: Shaunak Kashyap <[email protected]> Co-authored-by: Julien Lind <[email protected]>
What is the problem this PR solves?
This PR expects only a 400 HTTP response code from the Elasticsearch bulk API in integration tests when invalid index name is specified. Concretely, it removes the
AltErr
field temporarily introduced in #4001 which was allowing the tests to accept an alternate error from Elasticsearch.Related: elastic/elasticsearch#114869