uptasticsearch 0.3.0

Features

#64 added support for ES6.x. The biggest change between that major version and v5.x is that as of ES6.x all requests issued to the ES HTTP API must pass an explicit Content-Type header. Previous versions of ES tried to guess the Content-Type when none was declared
#66 completed support for ES6.x. ES6.x changed the supported strategy for issuing scrolling requests. uptasticsearch will now hit the cluster to try to figure out which version of ES it is running, then use the appropriate scrolling strategy.

previously, get_fields() broke on some legacy versions of Elasticsearch where no aliases had been created. The response on the _cat/aliases endpoint has changed from major version to major version. #66 fixed this for all major versions of ES from 1.0 to 6.2

previously, if you had multiple aliases pointing to the same physical index, get_fields() would only return one of those. As of #73, mappings for the underlying physical index will now be duplicated once per alias in the table returned by get_fields().

as of #64, uptasticsearch attempts to query the ES host to figure out what major version of Elasticsearch is running there. Implementation errors in that PR led to versions being parsed incorrectly but silently passing tests. This was fixed in #66. NOTE: this only impacted the dev version of the library on Github.

In previous versions of uptasticsearch, the value passed to es_search() for ignore_scroll_restriction was not actually respected. This was possible because an internal function had defaults specified, so we never caught the fact that that value wasn't getting passed through. #66 instituted the practice of not specifying defaults on function arguments in internal functions, so similar bugs won't be able to silently get through testing in the future.

#69 added a deprecation warning on get_counts(). This function was outside the core mission of the package and exposed us unnecessarily to changes in the Elasticsearch DSL.