<p dir="auto">Hi there,<br>
I am evaluating an upgrade to 1.7.1 for our 1.4.4 production cluster. We seem to be having some data that has geo shapes that 1.4.4 accepted and indexed but 1.7.1 is choking on. The message below is only a warning but it seems to be rejecting the whole shard to be moved to the newer versioned machine, right? Can I reduce the level of validation checking for geo locations?</p>
<p dir="auto">Do we have  a breaking change in geo shape validator between these versions?<br>
[2015-08-04 11:41:19,543][WARN ][cluster.action.shard ] [hostname] [indexname][5] received shard failed for [indexname][5], node[lxvTTQWSRDiBA9Se21hjHw], relocating [BRUHrGoBQnO9MzyssyMCoQ], [P], s[RELOCATING], indexUUID [d2E1eeDHRB6FOs57k0IxaA], reason [Failed to perform [indices:data/write/bulk[s]] on replica, message [RemoteTransportException[[hostname][inet[/10.10.10.220:9302]][indices:data/write/bulk[s][r]]]; nested: MapperParsingException[failed to parse [message.location.geo]]; nested: InvalidShapeException[Provided shape has duplicate consecutive coordinates at: (-88.097892, 37.771743, NaN)]; ]]</p>
<p dir="auto"><em>From <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/gabriel-tessier/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/gabriel-tessier">@gabriel-tessier</a> on July 17, 2015 2:56</em></p>
<p dir="auto">Hi,<br>
I need to update the user dictionary and I usually open close the index to make the change apply.<br>
One question: Is it the only way to update the dict cause in case of typo (missing a , or one bad space) in the file the index don't open at all and on production server it's not an option.<br>
first question (for confirmation): is it the good way to do? open close the index to reload the dict.<br>
second one: is there a way to have an option like check config for apache [apachectl configtest]? so we can open close the index without fear!!</p>
<p dir="auto">Thanks.</p>
<p dir="auto"><em>Copied from original issue: elastic/elasticsearch-analysis-kuromoji#65</em></p>