Doc Values

Is there a way to turn doc_values on cluster wide and override any index specific settings?

--
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/0f54a59e-7490-4c63-b223-6371fa49719a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

You can update mappings cluster-wide (just post the mapping definition to
server:9200/*), but you will need to specify the field names explicitly

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Sat, Feb 7, 2015 at 9:30 PM, Joel Baranick jbaranick@gmail.com wrote:

Is there a way to turn doc_values on cluster wide and override any index
specific settings?

--
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/0f54a59e-7490-4c63-b223-6371fa49719a%40googlegroups.com
.
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/CAHTr4Zu7aZudsPYCaMLTJGtngn9%2B3h7qny%2B4fYzksf%3DVrUmEEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Got it. What I was hoping for would be a way to force doc_values to be the only way for fielddata to be stored for all mapping a in the entire cluster without having to update each index. Could this be done with a plugin?

--
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/67ce9351-f37a-40aa-ad04-c5328140d6fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

If the indexes have been already created you will have to be creative to
find those fields that need updating - not familiar with a plugin that can
do that. A simple client side tool that will grab all mappings from the
/_mapping endpoint, change it and send it back should do

For indexes that weren't created yet you can use index templates

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Sat, Feb 7, 2015 at 10:04 PM, Joel Baranick jbaranick@gmail.com wrote:

Got it. What I was hoping for would be a way to force doc_values to be the
only way for fielddata to be stored for all mapping a in the entire cluster
without having to update each index. Could this be done with a plugin?

--
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/67ce9351-f37a-40aa-ad04-c5328140d6fd%40googlegroups.com
.
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/CAHTr4Zv6pffNZ2nZJMm0ew%2BPeaVX2GaNRoQdSHRXYD-x_T%2BARA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Thanks. I will look into if I can create a plugin which will automatically enable doc_values whenever an index is created or updated. This seems like it could be very useful for multitenant clusters.

--
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/032429bb-38de-40f1-8290-334a4890851d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

You don't need a plugin for index when an index is created - use index
templates + dynamic templates for this, e.g.
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/custom-dynamic-mapping.html#dynamic-templates

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Sat, Feb 7, 2015 at 11:56 PM, Joel Baranick jbaranick@gmail.com wrote:

Thanks. I will look into if I can create a plugin which will automatically
enable doc_values whenever an index is created or updated. This seems like
it could be very useful for multitenant clusters.

--
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/032429bb-38de-40f1-8290-334a4890851d%40googlegroups.com
.
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/CAHTr4ZuKav0hP6G%2BCM55t6r1pYh62%3DOY-eOQarMteEeVyDE7_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Sure. I get that, but I'm talking about a multi-tenant environment where I
do not control the index templates or mappings which are installed. In
this scenario it would be nice to be able to configure the cluster to only
allow field data to be off or doc_values.

On Saturday, February 7, 2015 at 1:58:00 PM UTC-8, Itamar Syn-Hershko wrote:

You don't need a plugin for index when an index is created - use index
templates + dynamic templates for this, e.g.
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/custom-dynamic-mapping.html#dynamic-templates

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Sat, Feb 7, 2015 at 11:56 PM, Joel Baranick <jbar...@gmail.com
<javascript:>> wrote:

Thanks. I will look into if I can create a plugin which will
automatically enable doc_values whenever an index is created or updated.
This seems like it could be very useful for multitenant clusters.

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/032429bb-38de-40f1-8290-334a4890851d%40googlegroups.com
.
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/96e8dea4-61bf-44bf-b14f-c38702b041f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Have a look at http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-templates.html#indices-templates

This will help IMO.

David

Le 8 févr. 2015 à 02:44, Joel Baranick jbaranick@gmail.com a écrit :

Sure. I get that, but I'm talking about a multi-tenant environment where I do not control the index templates or mappings which are installed. In this scenario it would be nice to be able to configure the cluster to only allow field data to be off or doc_values.

On Saturday, February 7, 2015 at 1:58:00 PM UTC-8, Itamar Syn-Hershko wrote:
You don't need a plugin for index when an index is created - use index templates + dynamic templates for this, e.g. http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/custom-dynamic-mapping.html#dynamic-templates

--

Itamar Syn-Hershko
http://code972.com | @synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Sat, Feb 7, 2015 at 11:56 PM, Joel Baranick jbar...@gmail.com wrote:
Thanks. I will look into if I can create a plugin which will automatically enable doc_values whenever an index is created or updated. This seems like it could be very useful for multitenant clusters.

--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/032429bb-38de-40f1-8290-334a4890851d%40googlegroups.com.
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/96e8dea4-61bf-44bf-b14f-c38702b041f5%40googlegroups.com.
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/9BDEB4CA-55A2-4AB7-BE76-0EBF0B1E2DCA%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Great! That does look pretty close. Guessing I could use an index template with order=int.max, set the template to * and configure the default mapping. Only thing I'm not sure about is how to restrict field data to either off or doc_values for fields whose names I do not know. Dynamic templates don't seem to work because they only apply if an explicit mapping doesn't exist. Any suggestions on what could be added to an index template which would achieve my goals?

--
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/83794a3b-5d5c-4f4e-b4cb-043d3d177c56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

May be some ideas here? https://github.com/elasticsearch/logstash/blob/v1.4.2/lib/logstash/outputs/elasticsearch/elasticsearch-template.json

David

Le 8 févr. 2015 à 06:25, Kadaan jbaranick@gmail.com a écrit :

Great! That does look pretty close. Guessing I could use an index template with order=int.max, set the template to * and configure the default mapping. Only thing I'm not sure about is how to restrict field data to either off or doc_values for fields whose names I do not know. Dynamic templates don't seem to work because they only apply if an explicit mapping doesn't exist. Any suggestions on what could be added to an index template which would achieve my goals?

--
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/83794a3b-5d5c-4f4e-b4cb-043d3d177c56%40googlegroups.com.
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/371AD867-7ECF-4EF2-96DE-CF33F671FF7B%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.