Hi all,
In the process of installing AtoM 2.0.1 today, we came across this backwards-compatibility issue with the recent ElasticSearch 1.0 release. In particular, ES has deprecated the {"OK" : true} part of their response, which is built into the logic during the AtoM installation process:
The fix in our case was simple, we just removed the check for the "OK" attribute in the response (ie. the first condition on that line); but I don't know if there are other places in the code where this fix might also have to be applied.
Given the massive communication and uptake around ElasticSearch 1.0, I figured it was worth mentioning this as soon as possible in case others encounter the same issue.
Cheers,
MJ