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

Fix _terms_enum default indices options #75172

Merged
merged 1 commit into from
Jul 9, 2021

Conversation

jimczi
Copy link
Contributor

@jimczi jimczi commented Jul 9, 2021

This commit changes the default indices options of the new terms enum API
to be consistent with _search.
This change also fixes the shards statistics in the response when ccs is involved.

Closes #75155

This commit changes the default indices options of the new terms enum API
to be consistent with _search.
This change also fixes the shards statistics in the response when ccs is involved.

Closes elastic#75155
@jimczi jimczi added >bug :Search/Search Search-related issues that do not fall into other categories v8.0.0 v7.14.1 v7.15.0 labels Jul 9, 2021
@jimczi jimczi requested a review from markharwood July 9, 2021 09:37
@elasticmachine elasticmachine added the Team:Search Meta label for search team label Jul 9, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (Team:Search)

Copy link
Contributor

@markharwood markharwood left a comment

Choose a reason for hiding this comment

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

LGTM. I assume we don't need to add CCS tests for the failing scenario because the existing tests for IndicesOptions should cover this scenario?


/**
* A request to gather terms for a given field matching a string prefix
*/
public class TermsEnumRequest extends BroadcastRequest<TermsEnumRequest> implements ToXContentObject {

public static final IndicesOptions DEFAULT_INDICES_OPTIONS = SearchRequest.DEFAULT_INDICES_OPTIONS;
Copy link
Contributor

Choose a reason for hiding this comment

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

Safe to assume terms_enum options will always be aligned with that of search?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's the intent of the PR, yes.

@jimczi jimczi merged commit 95469c3 into elastic:master Jul 9, 2021
@jimczi jimczi deleted the terms_enum_options branch July 9, 2021 11:36
jimczi added a commit to jimczi/elasticsearch that referenced this pull request Jul 9, 2021
This commit changes the default indices options of the new terms enum API
to be consistent with _search.
This change also fixes the shards statistics in the response when ccs is involved.

Closes elastic#75155
jimczi added a commit to jimczi/elasticsearch that referenced this pull request Jul 9, 2021
This commit changes the default indices options of the new terms enum API
to be consistent with _search.
This change also fixes the shards statistics in the response when ccs is involved.

Closes elastic#75155
jimczi added a commit that referenced this pull request Jul 9, 2021
This commit changes the default indices options of the new terms enum API
to be consistent with _search.
This change also fixes the shards statistics in the response when ccs is involved.

Closes #75155
@jimczi jimczi added >non-issue and removed >bug labels Jul 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>non-issue :Search/Search Search-related issues that do not fall into other categories Team:Search Meta label for search team v7.14.0 v7.15.0 v8.0.0-alpha1
Projects
None yet
5 participants