<p dir="auto">I'm not sure if this is a bug or corruption experienced during the upgrade but as of 1.2.0, we're now experiencing duplicate results in all queries:</p>
<p dir="auto">{<br>
took: 0<br>
timed_out: false<br>
_shards: {<br>
total: 5<br>
successful: 5<br>
failed: 0<br>
}<br>
hits: {<br>
total: 2<br>
max_score: 13.58639<br>
hits: [<br>
{<br>
_index: media6<br>
_type: Media<br>
_id: 534918829017389526_260014085,<br>
_score: 13.58639,<br>
_source: {}<br>
},<br>
{<br>
_index: media6<br>
_type: Media<br>
_id: 534918829017389526_260014085,<br>
_score: 12.815866,<br>
_source: {}<br>
}]<br>
}}</p>
<p dir="auto">There have been no changes to indexes, types, or other mappings. My understanding was that a unique ID really depends on index/type/id/routing.  The routing, by<br>
default, is derived from the ID. No parent-child relationships are in use here.</p>
<p dir="auto">Cross-posted but unrelated to sort as initially suspected:<br>
<a href="http://elasticsearch-users.115913.n3.nabble.com/Duplicate-Results-Following-Upgrade-to-1-2-0-amp-SortScript-td4056672.html" rel="nofollow">http://elasticsearch-users.115913.n3.nabble.com/Duplicate-Results-Following-Upgrade-to-1-2-0-amp-SortScript-td4056672.html</a></p>
<p dir="auto">Many people have some challenges when using Git/GitHub to contribute to the project.</p>
<p dir="auto">It would be nice to have a GitHub.CHEATSHEET similar to GRADLE.CHEATSHEET.</p>