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 <jbaran...@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+unsubscr...@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+unsubscr...@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.
