Set index.query.parse.allow_unmapped_fields = false for a single index

Hey guys,
We're running ES as a core service, so I can't guarantee that my
application will be the only one using the cluster. Is it possible to
disallow unmapped fields explicitly for an index without modifying the
global setting?

Thanks,
Todd

--
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/19b5a2f9-88f4-4100-809d-3e258e24f6af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Figured this out (derp). So my next question, is how can I disable dynamic
mappings so that they don't occur?

Thanks,
Todd

On Thursday, April 2, 2015 at 3:55:07 PM UTC-6, Todd Nine wrote:

Hey guys,
We're running ES as a core service, so I can't guarantee that my
application will be the only one using the cluster. Is it possible to
disallow unmapped fields explicitly for an index without modifying the
global setting?

Thanks,
Todd

--
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/29f0c5e3-068d-4e19-9a3b-6cd38ec60e08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

You can use index.mapper.dynamic: false

​See
http://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-mapper.html#_dynamic_mappings

On 3 April 2015 at 09:14, Todd Nine tnine@apigee.com wrote:

Figured this out (derp). So my next question, is how can I disable
dynamic mappings so that they don't occur?

Thanks,
Todd

On Thursday, April 2, 2015 at 3:55:07 PM UTC-6, Todd Nine wrote:

Hey guys,
We're running ES as a core service, so I can't guarantee that my
application will be the only one using the cluster. Is it possible to
disallow unmapped fields explicitly for an index without modifying the
global setting?

Thanks,
Todd

--
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/29f0c5e3-068d-4e19-9a3b-6cd38ec60e08%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/29f0c5e3-068d-4e19-9a3b-6cd38ec60e08%40googlegroups.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/CAEYi1X9pcUgD0oSEPFS-UWAOjjX8JqKbmVfaa0DC0PcZKtspvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.