Skip to content

Conversation

@cbuescher
Copy link
Member

Starting with Elasticsearch 7.0, we limit the number of automatically expanded
fields for the "all fields" mode ("default_field": "*") for the query_string and
simple_query_string queries to 1024 fields (see #26541). This change adds a
deprecation warning to the QueryParserHelper where in the next major version we
will throw an error to warn users of the upcoming change.

Relates to #26541

Starting with Elasticsearch 7.0, we limit the number of automatically expanded
fields for the "all fields" mode ("default_field": "*") for the query_string and
simple_query_string queries to 1024 fields (see elastic#26541). This change adds a
deprecation warning to the QueryParserHelper where in the next major version we
will throw an error to warn users of the upcoming change.

Relates to elastic#26541
@cbuescher cbuescher added :Search Foundations/Mapping Index mappings, including merging and defining field types >deprecation v6.6.0 v6.5.1 labels Oct 26, 2018
@cbuescher cbuescher requested a review from jimczi October 26, 2018 14:39
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search-aggs

@cbuescher
Copy link
Member Author

@jimczi this is meant as the follow up to yesterdays docs change (#34801). I think we also need some not in the migration docs, but as far as I understand I would need to add the note about the limit coming into effect on master, right? If so, I will do that in another PR, if I should add this to some 6.x migration doc please let me know in this PR. I always get confused where these notes should go.

Copy link
Contributor

@jimczi jimczi left a comment

Choose a reason for hiding this comment

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

LGTM, thanks @cbuescher

Copy link
Contributor

@jimczi jimczi left a comment

Choose a reason for hiding this comment

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

@cbuescher
Copy link
Member Author

You can add a deprecation note in https://github.com/elastic/elasticsearch/blob/6.x/docs/reference/migration/migrate_6_0/search.asciidoc

Isn't that document intended for migrations to 6.0? My understanding so far was that we add breaking changes in the versions that they should be adressed. That would be 7.0 for the limit introduced here, at least for the breaking change. https://github.com/elastic/elasticsearch/tree/6.x/docs/reference/migration/migrate_7_0 looks quite empty though, so I guess somewhere in https://github.com/elastic/elasticsearch/tree/master/docs/reference/migration/migrate_7_0 would be the right spot?
I will go ahead and add a deprecation note to https://github.com/elastic/elasticsearch/blob/6.x/docs/reference/migration/migrate_6_5.asciidoc#breaking_65_search_changes in this PR.

@cbuescher cbuescher removed the v6.5.1 label Oct 26, 2018
@cbuescher
Copy link
Member Author

I added deprecation notes in a new migrate_6_6.asciidoc in the last commit, I think its okay to only backport this change to the 6.x branch. Let me know if you disagree, otherwise I'll just merge to 6.x. I'll open a separate PR for the 7.0 migration notes.

Copy link
Contributor

@jimczi jimczi left a comment

Choose a reason for hiding this comment

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

Yep +1 for 6x only.

==== `query_string` and `simple_query_string` query

Using automatically expanded fields for the "all fields" mode ("default_field": "*")
for the `query_string` and `simple_query_string` now raises a warning and a deprecation
Copy link
Contributor

Choose a reason for hiding this comment

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

it is also applied to multi_match queries.

@cbuescher cbuescher merged commit 682b0d5 into elastic:6.x Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>deprecation :Search Foundations/Mapping Index mappings, including merging and defining field types v6.6.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants