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?
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
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?
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.
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.
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:
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.
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.
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.
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?
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?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.