Permalink
Commits on Jan 23, 2015
  1. Fix error in test_percolate in ES 1.4.

    erikrose committed Jan 23, 2015
    Add an explicit mapping to dodge "Strict field resolution and no field mapping can be found for the field with name [name]".
  2. Bump version to 1.0.

    erikrose committed Jan 23, 2015
    This aligns nicely with the versions of ES we support now, and I think future backward-incompatible changes will be few.
  3. Fix spuriously failing percolator test. Bring percolator es_kwargs up…

    erikrose committed Jan 23, 2015
    … to date.
    
    Get willkg's test fixes into the changelog as well.
  4. Fix cluster_state() to work with ES 1.0 and later.

    erikrose committed Jan 23, 2015
    Downgrade backward-incompatibility warnings to notes. The red in the default template made it look worse than it really was.
  5. Changes "services" to a list in Travis config.

    erikrose committed Jan 23, 2015
    Let's see if that gets rid of the connection errors.
    
    Also, don't install the package as editable. That avoids testing that the manifest is correct.
Commits on Jan 22, 2015
  1. Clean up some imports.

    erikrose committed Jan 22, 2015
  2. Use mock's ANY instead of our own WHATEVER.

    erikrose committed Jan 22, 2015
    Less code. Also, this lets us run tests under 2.6 without using the total-ordering package.
    
    Also remove the unused eq_one_of().
  3. Remove ``encode_body`` param from ``send_request()``.

    erikrose committed Jan 22, 2015
    Now all dicts are JSON-encoded, and all strings are left alone.
  4. Make ElasticSearch._transport private. I don't want to give the impre…

    erikrose committed Jan 22, 2015
    …ssion that you should go poking around at it.
  5. Remove tests for ES < 1.0.

    erikrose committed Jan 22, 2015
    We don't support old versions anymore because it would make our elasticsearch-py dependency hard to manage: they don't support both pre- and post-1.0 in any one version.
    
    Also fix test_multi_get_simple, which would pass no matter what.
    
    The remaining 3 test failures are due to ES API changes that outrun us. We can fix them on master.
  6. Wrap to use our original exception hierarchy.

    erikrose committed Jan 22, 2015
    Also remove a test of InvalidJsonResponseError, which is no more.
    
    Add a dummy URL in es_kwarg_tests so ElasticSearch will construct without blowing up.
Commits on Jan 21, 2015
  1. Restore _to_query(). It turns out stringification remains our respons…

    erikrose committed Jan 21, 2015
    …ibility for now.
    
    test_index now passes.
    
    (I haven't looked to see whether elasticsearch-py's is as good as ours.)
  2. Merge test fixes which get us passing all but 3 for 0.90 through 1.3. C…

    erikrose committed Jan 21, 2015
    …lose #158.
    
    The failures are because the relevant ElasticSearch client methods are broken with Elasticsearch 1.0+. Those are covered in other issues.
  3. Switch to elasticsearch-py's transport layer. Ref #135, #109. Bump ve…

    erikrose committed Jan 21, 2015
    …rsion to 0.8.0.
    
    This loses ES < 1.0 compat and makes indexing crazy faster. We're not supporting any transports but HTTP at the moment, as they don't thrill me. (Thrift might get you a 15% boost but only if you have lots of small requests.)
Commits on Dec 18, 2014
Commits on Aug 14, 2014
  1. Tolerate errors that are non-strings. Close #116.

    erikrose committed Aug 14, 2014
    Commit message from original patch author konradkonrad:
    
    The code from _raise_exception expected a string here, which e.g.
    for FetchPhaseExecutionException is not the case and yields an
    "AttributeError: 'dict' object has no attribute 'startswith'".
    
    In such a case the exact error_messages would be in response body in
    [shard['reason'] for shard in response_body['_shards']['failures']].
    
    This checks for a string and just returns the whole response_body
    otherwise, so the elasticsearch exception becomes visible to the
    user.
Commits on Aug 12, 2014
  1. Bring readme up to date.

    erikrose committed Aug 12, 2014
  2. ``update_aliases()`` no longer requires a dict with an ``actions`` ke…

    erikrose committed Aug 12, 2014
    …y; that much is implied.
  3. Rename ``aliases()`` to ``get_aliases()`` for consistency with other …

    erikrose committed Aug 12, 2014
    …methods. Add an ``alias`` kwarg.
Commits on May 21, 2014
  1. Adapt to use elasticsearch-py's transport layer. (Address is hard-cod…

    erikrose committed May 21, 2014
    …ed in. Dead code is still hanging out.)