Upgrade to Elasticsearch 1.3.0

[lukas-vlcek]

Not urgent but we should do it soon. There were bunch API changes and improvements.

[lukas-vlcek]

It seems that we might be hitting River does not start #4089 issue while we are on 0.90.5. In particular in our case rivers do not start on multinode cluster when the cluster is restarted (as long as the cluster is single node it is not an issue).
This can be problematic wrt to Searchisko production upgrades. Because of this we should give upgrading to ES 1.x higher priority.

[lukas-vlcek]

Facets are officially deprecated: elastic/elasticsearch#6485 (starting with ES 1.3)

[velias]

elasticsearch-river-remote, elasticsearch-river-jira and structured-content-tools for ES 1.2.x are available already

[lukas-vlcek]

We also need to keep an eye on changes to CORS support in Elasticsearch (seems most changes are happening from 1.4). Currently CORS is handled partly by Searchisko servlet filter and partly it is delegated to Elasticsearch thus we will be hit by this change.

See: elastic/elasticsearch#6380, elastic/elasticsearch#7151

[unibrew]

I also vote for 1.4. because then aggregations come to ES and I could find a use for them in my stats APIs implementation.

[lukas-vlcek]

We will be upgrading from Elasticsearch 0.90.5 to 1.x. Official upgrade notes:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/setup-upgrade.html (note the restart upgrade is recommended).

[lukas-vlcek]

Both api and ftest tests pass.

The following are details about changes in Elasticsearch code that have impact:

ElasticSearchException -> ElasticsearchException

Ticket:
elastic/elasticsearch#4634

setFilter -> setPostFilter

Commit:
elastic/elasticsearch@23d2b1e

Ticket:
elastic/elasticsearch#4119

DeleteResponse.isNotFound() -> DeleteResponse.isFound()

Commits:
elastic/elasticsearch@2cb40fc#diff-12, elastic/elasticsearch@4c06c53

InternalSearchHit changes constructor signature

Commit:
elastic/elasticsearch@668d557#diff-26

(Multi)SearchRequestBuilder does not accept null in constructor

Mocking Client seems to fix it.

Removed ok return value

Impact on integration tests.

Ticket:
elastic/elasticsearch#4310