Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Mar 5, 2015
  1. @willkg
Commits on Jan 5, 2015
  1. @willkg

    Cosmetic: Fix CHANGELOG typo

    willkg 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 Sep 22, 2014
  1. @willkg
  2. @willkg

    Update CHANGELOG for 0.10.1

    willkg authored
Commits on Sep 11, 2014
  1. @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.
Commits on Aug 19, 2014
  1. @willkg
  2. @willkg

    Update version for 0.10 release

    willkg authored
  3. @willkg
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 May 20, 2014
  1. @willkg
  2. @willkg

    Add note about Python 3 support

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

    Update CHANGELOG

    willkg authored
  2. @willkg

    Update date for 0.9 release

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

    Update CHANGELOG

    willkg authored
    * add note about ESTestCase
  2. @willkg

    Update CHANGELOG

    willkg authored
    * add facet_count changes
Commits on Mar 19, 2014
  1. @willkg
Commits on Mar 18, 2014
  1. @willkg

    Move results metadata to es_meta object

    willkg authored
    Django templates don't allow you to expose variables that start with an
    _. So having:
    
        obj._highlight
    
    sucked.
    
    We've got a fair number of these metadata items and I'm concerned with
    each new one we add, we increase the likelihood that there's a naming
    conflict with actual data.
    
    So this moves all those items into an es_meta object which you can
    access like this:
    
        obj.es_meta.highlight
    
    The one exception is _id--you can now access the id Elasticsearch gives
    the document with both:
    
        obj._id
    
    and:
    
        obj.es_meta.id
    
    Fixes #205
Commits on Mar 13, 2014
  1. @willkg
Commits on Feb 28, 2014
  1. @willkg

    Switch .all() to .everything()

    willkg authored
    * switch the old .all() to .everything()
    * change .all() to be more like what Django ModelManager/QuerySet does
    
    Fixes #200
  2. @willkg
  3. @willkg

    Restrict elasticsearch-py to specific versions

    willkg authored
    elasticsearch-py 1.0 made a bunch of changes we're not going to support
    with ElasticUtils 0.9. We'll support them in the next version.
Commits on Jan 31, 2014
  1. @willkg

    Update CHANGELOG

    willkg authored
  2. @willkg

    Update CHANGELOG

    willkg authored
  3. @willkg
Commits on Nov 20, 2013
  1. @willkg
Commits on Sep 13, 2013
  1. @willkg
  2. @willkg

    Fix silly typo in CHANGELOG

    willkg authored
  3. @willkg
Commits on Aug 19, 2013
  1. @willkg

    Update to 0.8 for release; peg pyelsticsearch

    willkg authored
    We're pegging to a specific version of pyelasticsearch since they've
    done a release that had backwards-incompatible changes.
    
    Updated the release process accordingly.
    
    Moved requirements files to their own directory to clean things up
    a smidge.
Commits on Aug 7, 2013
  1. @willkg

    Update CHANGELOG

    willkg authored
Something went wrong with that request. Please try again.