Skip to content
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

Cleanup construction of interceptors #38294

Merged
merged 2 commits into from
Feb 4, 2019

Conversation

tvernum
Copy link
Contributor

@tvernum tvernum commented Feb 4, 2019

It would be beneficial to apply some of the request interceptors even
when features are disabled. This change reworks the way we build that
list so that the interceptors we always want to use are constructed
outside of the settings check.

It would be beneficial to apply some of the request interceptors even
when features are disabled. This change reworks the way we build that
list so that the interceptors we always want to use are constructed
outside of the settings check.
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@tvernum tvernum requested a review from jaymode February 4, 2019 04:05
Copy link
Member

@jaymode jaymode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tvernum
Copy link
Contributor Author

tvernum commented Feb 4, 2019

04:21:51 |    [2019-02-04T04:21:51,068][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [node-0] fatal error in thread [elasticsearch[node-0][generic][T#5]], exiting
04:21:51 |    java.lang.AssertionError: primary_term:1;version:0;

@elasticmachine run elasticsearch-ci/default-distro

@tvernum tvernum merged commit 0164acb into elastic:master Feb 4, 2019
tvernum added a commit to tvernum/elasticsearch that referenced this pull request Feb 4, 2019
It would be beneficial to apply some of the request interceptors even
when features are disabled. This change reworks the way we build that
list so that the interceptors we always want to use are constructed
outside of the settings check.

Backport of: elastic#38294
tvernum added a commit that referenced this pull request Feb 4, 2019
It would be beneficial to apply some of the request interceptors even
when features are disabled. This change reworks the way we build that
list so that the interceptors we always want to use are constructed
outside of the settings check.

Backport of: #38294
tvernum added a commit to tvernum/elasticsearch that referenced this pull request Feb 5, 2019
It would be beneficial to apply some of the request interceptors even
when features are disabled. This change reworks the way we build that
list so that the interceptors we always want to use are constructed
outside of the settings check.
Backport of: elastic#38294
tvernum added a commit that referenced this pull request Feb 5, 2019
It would be beneficial to apply some of the request interceptors even
when features are disabled. This change reworks the way we build that
list so that the interceptors we always want to use are constructed
outside of the settings check.

Backport of: #38294
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants