Skip to content

Warn if using no default field with large mapping#35570

Merged
cbuescher merged 3 commits intomasterfrom
geekpete-patch-docs-querystring-1
Nov 19, 2018
Merged

Warn if using no default field with large mapping#35570
cbuescher merged 3 commits intomasterfrom
geekpete-patch-docs-querystring-1

Conversation

@geekpete
Copy link
Copy Markdown
Contributor

Warn about potential performance impact when a large number of fields in mapping with _source disabled is used with query string query and no default field.

Warn about potential performance impact when a large number of fields in mapping with _source disabled is used with query string query and no default field.
@geekpete geekpete added >docs General docs changes :Search/Search Search-related issues that do not fall into other categories labels Nov 14, 2018
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-search-aggs

Copy link
Copy Markdown
Member

@cbuescher cbuescher left a comment

Choose a reason for hiding this comment

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

Hi @geekpete, I left a note, can you take a look at the part above in this doc and let me know if that would cover what you would like to add here?

Also wrapped at 80 columns
Copy link
Copy Markdown
Member

@cbuescher cbuescher left a comment

Choose a reason for hiding this comment

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

Thanks for the change, LGTM.

@geekpete
Copy link
Copy Markdown
Contributor Author

@elasticmachine retest this please

@cbuescher cbuescher merged commit 6d8af97 into master Nov 19, 2018
cbuescher pushed a commit that referenced this pull request Nov 19, 2018
)

Warn about potential performance impact when a large number of fields
is used with query string query and no default field.
@geekpete geekpete deleted the geekpete-patch-docs-querystring-1 branch December 3, 2018 02:37
jrodewig added a commit that referenced this pull request Apr 28, 2020
)

Warn about potential performance impact when a large number of fields
is used with query string query and no default field.

Re-adds content from #35570.
That content was erroneously removed in #45296.

Co-authored-by: Peter Dyson <peter.dyson@geekpete.com>
jrodewig added a commit that referenced this pull request Apr 28, 2020
)

Warn about potential performance impact when a large number of fields
is used with query string query and no default field.

Re-adds content from #35570.
That content was erroneously removed in #45296.

Co-authored-by: Peter Dyson <peter.dyson@geekpete.com>
jrodewig added a commit that referenced this pull request Apr 28, 2020
)

Warn about potential performance impact when a large number of fields
is used with query string query and no default field.

Re-adds content from #35570.
That content was erroneously removed in #45296.

Co-authored-by: Peter Dyson <peter.dyson@geekpete.com>
jrodewig added a commit that referenced this pull request Apr 28, 2020
)

Warn about potential performance impact when a large number of fields
is used with query string query and no default field.

Re-adds content from #35570.
That content was erroneously removed in #45296.

Co-authored-by: Peter Dyson <peter.dyson@geekpete.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>docs General docs changes :Search/Search Search-related issues that do not fall into other categories v6.6.0 v7.0.0-beta1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants