What examples are you referring to? The only reason I could think of why you'd do this is because the best way to deal with bulk deletes and mass mapping changes in Elasticsearch is to create a new index and use aliases to point pretty named indices at the newly created index before deleting the old one. However, I would always create the new index first, switch the alias and only then delete the old index.
On Tuesday, April 8, 2014 4:36:29 PM UTC+1, IronMan2014 wrote: > > All the examples I have seen so far, check if an index exist, delete it > and then create the index. > But in a production environment, isn't the normal to check if the index > doesn't exist, then create it. But if it does exist, then do nothing, > because typically the index exists and all we need to do is just index new > documents? > > Am I missing the point? > -- 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/aa92a79b-3fe5-4346-892c-99ae8c9587d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
