I would prefer having a script file which do everything you need than storing mappings in config/
I find scripts more flexible. You can create index with specific settings, add mapping, inject some data... My 2 cents. -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 5 août 2014 à 23:43, Hayden Muhl <[email protected]> a écrit : We've been using Solr for the past several months, but have been considering Elasticsearch recently. One think I can't quite wrap my head around is how to keep track of Elasticsearch cluster configuration. Solr is largely based on config files written in XML. These are very straight forward to handle. You store them in your repository, and when deploying a new system, you drop the config files in the right places and start up Solr. Elasticsearch configuration all seems to happen via the API. If I set up a cluster for QA, and get it configured the way I want, how would I then go about deploying a production environment with the same configuration? What processes do people here use for deploying new environments? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8DED0EB4-0BCB-4EFE-984D-AFCD54C648BA%40pilato.fr. For more options, visit https://groups.google.com/d/optout.
