Hi Josh, Creating a broken mapping shouldn't be possible and sounds like a serious bug. Can you gist your broken mapping ? I would like to see if I can figure out how it happened (if you know it will be great). Also - what version of ES are you using?
I hope that seeing the mapping I can up with a work around. There are a couple of other options but choosing one depends on the amount data you have and wether you're OK with some down time. Cheers, Boaz On Thursday, August 28, 2014 11:55:04 PM UTC+2, Joshua Montgomery wrote: > > Is it possible to fix the state file if its been corrupted. Somehow a bad > mapping was added and it had an extra '}' throwing the entire state file > off. Deleting the bad mapping didn't fix the issue. Do I need to rebuild > the entire cluster or is there a quick fix? Should Elasticsearch even allow > bad mappings? > > Also is it a good idea to run the cluster with this issue. > > Thanks, > -Josh > -- 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/40f587b5-35c8-428e-a68c-bebacc843637%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
