Now all dicts are JSON-encoded, and all strings are left alone.
…ssion that you should go poking around at it.
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.
…ibility for now. test_index now passes. (I haven't looked to see whether elasticsearch-py's is as good as ours.)
… Close #158. The failures are because the relevant ElasticSearch client methods are broken with Elasticsearch 1.0+. Those are covered in other issues.
…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.)
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+.
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
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.
…y; that much is implied.
…methods. Add an ``alias`` kwarg.
…ed in. Dead code is still hanging out.)
…ster at bulk indexing.