Elasticutils

===================================

.. Warning::

Development on this project has ceased. There will be no 0.11.

===============================

**Changes:**

* Added support for terms_stats facet.

==================================

.. Note::

This has been tested with Elasticsearch 0.90 up through 1.3.4.
We don't support versions of earlier than 0.90.

This supports elasticsearch-py >= 1.0.

This is a bridging release to help people migrate from Elasticsearch
<= 0.90 to Elasticsearch >= 1.0.

The next version of ElasticUtils will not support versions of
Elasticsearch < 1.0.

**Changes:**

* Fixed monkeypatch to work with all bulk op_types (e.g. insert,
create, update and delete)

====================================

.. Note::

This supports Elasticsearch 0.90, 1.0, 1.1 and 1.2. It doesn't
support versions earlier than 0.90 or later than 1.2.

This supports elasticsearch-py >= 1.0.

This is a bridging release to help people migrate from Elasticsearch
<= 0.90 to Elasticsearch >= 1.0.

The next version of ElasticUtils will not support versions of
Elasticsearch < 1.0.


**API-breaking changes:**

* **requires elasticsearch-py >= 1.0**

**Changes:**

* Add distance filter

* Fix tests to work with Elasticsearch 1.2

* Invert monkeypatch for bulk indexing

* Fix infinite recursion when pickling MappingType instances

* Invert monkeypatch--ElasticUtils now requires elasticsearch-py >= 1.0

===============================

.. Note::

This version supports Elasticsearch 0.90, 1.0 and 1.1. It does not
support versions earlier than 0.90 or later than 1.1.

ElasticUtils 0.10 does not work with elasticsearch-py > 0.4.5.

This is a bridging release to help people migrate from Elasticsearch
<= 0.90 to Elasticsearch >= 1.0.

The next version of ElasticUtils will not support versions of
Elasticsearch < 1.0.


**API-breaking changes:**

* **big ``.values_list()`` and ``.values_dict()`` changes**

``.values_list()`` and ``.values_dict()`` will now **always** specify
the Elasticsearch ``fields`` property.

If you call these two functions with no arguments (i.e. you specify
no fields), they will send ``fields=*`` to Elasticsearch. It will
send any fields marked as stored in the document mapping. If you
have no fields marked as stored, then it will return the id and type
of the result.

If you call these two functions with arguments (i.e. you specify
fields), then it'll return those fields---same as before.

However, they now return all values as lists. For example::

>>> S().values_list()
[([100], ['bob'], [40]), ...]

>>> S().values_list('id')
[([100],), ([101],), ...]

>>> S().values_dict()
[({'id': [100], 'name': ['bob'], 'weight': [40]}), ...]

>>> S().values_dict('id', 'name')
[({'id': [100], 'name': ['bob']}), ...]

* Removed ``text`` and ``text_phrase`` queries. They're renamed
in Elasticsearch to ``match`` and ``match_phrase``.

* Removed ``startswith`` query. Replace uses of it with ``prefix``.

**Changes:**

* Python 3 support (Python >= 3.3)

* Supports Elasticsearch 0.90, 1.0 and 1.1

==============================

**Changes:**

* **Fixed bug with facets that are both sized and filtered**