Doc_values for non analyzed fields

Elastic Stack Elasticsearch
1

Hi,
Will it make any difference in terms of field data memory, if I set the
field data format to doc_values for all fields that have mapping "index" :
"no" ?

Are these (non-analyzed) fields ever loaded in memory on first place ?

Example field mapping :
"rot": {
"index": "no",
"type": "integer"
}

I don't need to query on these fields, but i need to fetch them .
Any negative impact on my queries ?

Thank you
Georgi

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f4379be6-f750-4703-a163-211e7a6e0501%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Doc values cannot be used to fetch values, they are only used for sorting,
scripts and aggregations. It is like fielddata, but computed at indexing
time and stored on disk.

On Fri, Nov 28, 2014 at 4:07 PM, Georgi Ivanov georgi.r.ivanov@gmail.com
wrote:

Hi,
Will it make any difference in terms of field data memory, if I set the
field data format to doc_values for all fields that have mapping "index" :
"no" ?

Are these (non-analyzed) fields ever loaded in memory on first place ?

Example field mapping :
"rot": {
"index": "no",
"type": "integer"
}

I don't need to query on these fields, but i need to fetch them .
Any negative impact on my queries ?

Thank you
Georgi

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f4379be6-f750-4703-a163-211e7a6e0501%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/f4379be6-f750-4703-a163-211e7a6e0501%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
Adrien Grand

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j5eK7qP9WVcLOSj0BhaRKk-%2BCftNwwH4HdFEbm%3DdJoKUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

So,
There is no sense to reindex everything just to set doc_value to non
analyzed fields.
Non indexed fields are not in the field data anyway

Right ?

2014-11-29 11:50 GMT+01:00 Adrien Grand adrien.grand@elasticsearch.com:

Doc values cannot be used to fetch values, they are only used for sorting,
scripts and aggregations. It is like fielddata, but computed at indexing
time and stored on disk.

On Fri, Nov 28, 2014 at 4:07 PM, Georgi Ivanov georgi.r.ivanov@gmail.com
wrote:

Hi,
Will it make any difference in terms of field data memory, if I set the
field data format to doc_values for all fields that have mapping "index" :
"no" ?

Are these (non-analyzed) fields ever loaded in memory on first place ?

Example field mapping :
"rot": {
"index": "no",
"type": "integer"
}

I don't need to query on these fields, but i need to fetch them .
Any negative impact on my queries ?

Thank you
Georgi

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f4379be6-f750-4703-a163-211e7a6e0501%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/f4379be6-f750-4703-a163-211e7a6e0501%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
Adrien Grand

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/EQnqv0tm75c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j5eK7qP9WVcLOSj0BhaRKk-%2BCftNwwH4HdFEbm%3DdJoKUQ%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j5eK7qP9WVcLOSj0BhaRKk-%2BCftNwwH4HdFEbm%3DdJoKUQ%40mail.gmail.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGKxwg%3D6mycKc60NocPE7LrvJjJDDu3r2w31qX_dLo0QXQziFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.