-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Update documentation for ES>=6.0 on sparsity for doc values & norms. #30833
Labels
>docs
General docs changes
:Search/Search
Search-related issues that do not fall into other categories
Comments
polyfractal
added
>docs
General docs changes
:Search/Search
Search-related issues that do not fall into other categories
labels
May 24, 2018
Pinging @elastic/es-search-aggs |
jpountz
added a commit
to jpountz/elasticsearch
that referenced
this issue
May 28, 2018
Sparsity is less of a concern since 6.03 Closes elastic#30833
jpountz
added a commit
that referenced
this issue
Jun 5, 2018
Sparsity is less of a concern since 6.0. Closes #30833
jpountz
added a commit
that referenced
this issue
Jun 5, 2018
Sparsity is less of a concern since 6.0. Closes #30833
jasontedor
pushed a commit
that referenced
this issue
Oct 15, 2018
Sparsity is less of a concern since 6.0. Closes #30833
jasontedor
pushed a commit
that referenced
this issue
Oct 15, 2018
Sparsity is less of a concern since 6.0. Closes #30833
jasontedor
pushed a commit
that referenced
this issue
Oct 15, 2018
Sparsity is less of a concern since 6.0. Closes #30833
jasontedor
pushed a commit
that referenced
this issue
Oct 15, 2018
Sparsity is less of a concern since 6.0. Closes #30833
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
I'm filing this documentation update request as a result of this forum thread: https://discuss.elastic.co/t/in-es-6-0-is-sparsity-for-doc-values-norms-still-bad/132946
Essentially, with Lucene 7, used in ES 6.0 and up, it seems to be no longer true that if a document doesn't have a field that other documents in the index have, the field still takes disk space for doc values and norms. See http://blog.mikemccandless.com/2017/03/apache-lucene-70-is-coming-soon.html
However, this bit of documentation, for ES versions 6.0, 6.1, 6.2, and 6.3 (as of now), still says that disk space is taken: https://www.elastic.co/guide/en/elasticsearch/reference/6.0/general-recommendations.html#sparsity
If my understanding is correct, could you please update the documentation?
The text was updated successfully, but these errors were encountered: