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

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

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

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

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

    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.
    erikrose committed Jan 23, 2015
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.

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

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

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

    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.
    erikrose committed Jan 22, 2015
  6. Wrap to use our original exception hierarchy.

    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.
    erikrose committed Jan 22, 2015
Commits on Jan 21, 2015
  1. Restore _to_query(). It turns out stringification remains our respons…

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

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

    …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.)
    erikrose committed Jan 21, 2015
Commits on Jan 7, 2015
  1. Fix tests to pass with ES 0.90 through ES 1.3.4

    This fixes the tests to pass with Elasticsearch 0.90 through
    Elasticsearch 1.3.4.
    
    Some of the fixes use eq_one_of which allows us to run multiple test
    conditions and as long as one of them passes, we're fine. This allows us
    to handle the change in HTTP responses from Elasticsearch between 0.90
    and 1.0+.
    willkg committed Jan 7, 2015
Commits on Jan 6, 2015
  1. Fix problem with fluctuating scores in tests

    The tests were such that they only passed on a specific version of
    Elasticsearch because they compared against specific scores in the
    results.
    
    Since we don't actually care about what the scores are, we do this
    sleight-of-hand with WHATEVER which happily compares positively with
    everything.
    
    This fixes the tests so everything passes in Elasticsearch 0.90.10.
    
    Fixes #107
    willkg committed Jan 6, 2015
  2. Fix tests balking on create_index

    After we call create_index, we need to wait a smidge for the index to be
    ready before we turn around and close it. This prevents
    IndexPrimaryShardNotAllocatedException errors.
    willkg committed Jan 6, 2015
Commits on Dec 18, 2014
Commits on Dec 9, 2014
  1. Fix delete query error in elasticsearch

    Change elasticsearch API to query delete in last versions.
    
    Old format:
    { 
       "query_string" : { 
            "query" : "some_query"     
       } 
    } 
    
    New format(after version 1.2.0 or early):
    { 
       "query" : { //added 
        "query_string" : { 
             "query" : "some_query"     
        } 
        } 
    }
    Detonavomek committed Dec 9, 2014
Commits on Aug 14, 2014
  1. Tolerate errors that are non-strings. Close #116.

    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.
    erikrose committed Aug 14, 2014
Commits on Aug 12, 2014