Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Mar 5, 2015
  1. @willkg
  2. @mythmon

    Add term_stats facet type.

    mythmon authored
Commits on Oct 10, 2014
  1. @willkg

    Prepare for 0.11 development

    willkg authored
  2. @willkg

    Prepare for 0.10.2 release

    willkg authored
Commits on Oct 9, 2014
  1. @willkg

    Fix bulk monkeypatch to work with non-insert op_types

    willkg authored
    This also adds a test for the monkeypatch to make sure it works with the
    various bulk op_types.
    
    Fixes #266
Commits on Sep 22, 2014
  1. @willkg
  2. @willkg
  3. @willkg
  4. @willkg

    Merge pull request #263 from batlock666/master

    willkg authored
    Fix infinite recursion when unpickling a mapping type instance
Commits on Sep 18, 2014
  1. Fix infinite recursion when unpickling a mapping type instance

    Bert Vanderbauwhede authored
Commits on Sep 11, 2014
  1. @willkg

    Update requirements to elasticsearch >= 1.0

    willkg authored
    This inverts the monkeypatch so that we can continue to work with
    ElasticUtils 0.90, but use elasticsearch-py >= 1.0. That makes things a
    lot easier going forward.
    
    Fixes #261
  2. @willkg

    Tweaking the version for 0.10.1 development

    willkg authored
    We're going to push out a 0.10.1 before moving on to 0.11.
  3. @willkg

    Fix index creation problems

    willkg authored
    When defining a mapping, the fields need to be in a 'properties' dict.
    Elasticsearch < 1.2 didn't complain about these, but Elasticseach 1.2
    does.
Commits on Sep 2, 2014
  1. @patrick91
Commits on Aug 28, 2014
  1. @patrick91

    Added distance filter.

    patrick91 authored
Commits on Aug 19, 2014
  1. @willkg
  2. @willkg

    Update version for 0.10 release

    willkg authored
Commits on Aug 18, 2014
  1. @willkg

    Fix S's values_list/dict re: ES 1.0

    willkg authored
    This makes some pretty big changes.
    
    1. .values_list() and .values_dict() will now **always** send the
       "fields" property to ES. If you don't specify any field arguments,
       then "fields=[*]". If you do specify fields arguments, then it'll
       be that list of fields.
    
    2. Elasticsearch 1.0 changed the shape of what gets returned--all
       values are lists when you specify the "fields" property. To
       make Elasticsearch 0.90 and Elasticsearch 1.0 consistent, we
       now convert any non-list values into list values for Elasticsearch
       0.90.
    
    Wait, wat? Prior to this commit, you'd have the following:
    
        # Elasticsearch 0.90
        >>> list(S().values_list())
        [(501, 'frank'), (602, 'sam')]           # values are ints and strings
    
        >>> list(S().values_list('id', 'name'))
        [(501, 'frank'), (602, 'sam')]           # values are ints and strings
    
        # Elasticsearch 1.0
        >>> list(S().values_list())
        [(501, 'frank'), (602, 'sam')]           # values are ints and strings
    
        >>> list(S().values_list('id', 'name'))
        [([501], ['frank']), ([602], ['sam'])]   # values are all lists
    
    After this change, we have this (assuming id and name fields are stored):
    
        # Elasticsearch 0.90
        >>> list(S().values_list())
        [([501], ['frank']), ([602], ['sam'])]
    
        >>> list(S().values_list('id'))
        [([501], ['frank']), ([602], ['sam'])]
    
        # Elasticsearch 1.0
        >>> list(S().values_list())
        [([501], ['frank']), ([602], ['sam'])]
    
        >>> list(S().values_list('id'))
        [([501], ['frank']), ([602], ['sam'])]
    
    If you plan to call .values_list() and .values_dict() with no arguments,
    you must add "store: True" to your mappings for the fields you want to
    get back.
Commits on Aug 13, 2014
  1. @willkg

    Invert Python2 checks to use PY3

    willkg authored
    six didn't always have a PY2, so this makes elasticutils work with older
    versions of six.
Commits on Aug 12, 2014
  1. @willkg

    Fix bulk indexing problems with Elasticsearch 1.0

    willkg authored
    In order for ElasticUtils to work for both Elasticsearch 0.90 and
    Elasticsearch 1.0 using elasticsearch-py 0.4.5, we need to do some
    monkey-patching of elasticsearch-py.
    
    In this case, calling Elasticsearch.client.bulk() returns an 'ok' field
    with ES 0.90 and a 'status' field with ES 1.0. This patch sets the 'ok'
    field based on the 'status' field so that the bulk indexing
    infrastructure in elasticsearch-py 0.4.5 is testing the right thing and
    not raising BulkIndexingErrors.
    
    Fixes #241
Commits on May 20, 2014
  1. @willkg
Commits on May 19, 2014
  1. @willkg
  2. @willkg

    Merge pull request #231 from eire1130/python3

    willkg authored
    Python3
Commits on May 9, 2014
  1. @jezdez

    Show which attribute wasn't able to be found.

    jezdez authored
    This should simplify debugging.
Commits on Apr 8, 2014
  1. @eire1130

    python3 cleanup

    eire1130 authored
  2. @eire1130

    python3

    eire1130 authored
Commits on Apr 7, 2014
  1. @willkg
  2. @willkg
  3. @willkg

    Fix facets that are filtered and sized

    willkg authored
    The if block was in the wrong place. Boo.
    
    This tweaks the existing test_facet_with_size so it's clearer. This adds
    a new test for facet that's both sized and filtered.
    
    Fixes #228
Commits on Apr 3, 2014
  1. @willkg

    Update version for v0.10.dev

    willkg authored
  2. @willkg
  3. @willkg

    Add a __repr__ to FacetResult

    willkg authored
Commits on Mar 26, 2014
  1. @willkg

    Add elasticutils.estestcase.ESTestCase

    willkg authored
    This makes the ESTestCase "public". Previously, it was intertwined with
    our test suite.
    
    Further, it adds documentation for it to the api.
    
    In the process of doing that, I nixed a bunch of skip_tests stuff. If
    someone doesn't want it to run tests, they should wrap the class on
    their own. That's a lot easier than us providing scaffolding that is
    either generic (hard) or requires a specific test framework
    (pain-in-the-ass-for-users).
    
    Fixes #215
  2. @willkg
  3. @willkg
Something went wrong with that request. Please try again.