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
Fix GET index API always running all features #8392
Conversation
} | ||
if (settings != null) { | ||
this.settings = settings; | ||
} |
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.
what happens if we assign to null? wondering why these checks are needed
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.
To be backwards compatible we need to return empty objects rather than null for features that return null from the request
@javanna have pushed a new iteration. Let me know what you think |
@@ -43,7 +111,15 @@ public GetIndexRequest features(String[] features) { | |||
return this; | |||
} | |||
|
|||
public String[] features() { |
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.
I think we should leave this method for java api bw comp
LGTM |
Previous to this change all features (_alias,_mapping,_settings,_warmer) are run regardless of which features are actually requested. This change fixes the request object to resolve this bug
merged into master, for 1.x and 1.4 changes see https://github.com/elasticsearch/elasticsearch/pull/8452/files |
Previous to this change all features (_alias,_mapping,_settings,_warmer) are run regardless of which features are actually requested. This change fixes the request object to resolve this bug