Skip to content
Commits on Nov 7, 2011
  1. Update tire.gemspec

    committed Nov 6, 2011
Commits on Nov 6, 2011
  1. Update tire.gemspec

    committed Nov 6, 2011
  2. @dylanahsmith @karmi
Commits on Nov 4, 2011
  1. @karmi

    [FIX] [REFACTORING] Extracted getting the response body to Logger#log…

    …ged in index methods
    karmi committed Nov 4, 2011
  2. @karmi
  3. @karmi
  4. @karmi
Commits on Oct 30, 2011
  1. @karmi

    Release 0.3.9

    karmi committed Oct 30, 2011
  2. @karmi
  3. @karmi

    Amended integration tests for the "custom_score" queries [#133] [#139]

    Also updated docs in examples/tire-dsl.rb.
    karmi committed Oct 30, 2011
  4. @karmi
Commits on Oct 28, 2011
  1. @dylanahsmith @karmi

    [FIX] Avoid doing a map if wrapper is Hash

    This also speeds up map by moving the check out of the block.
    
    Closes #135.
    dylanahsmith committed with karmi Oct 25, 2011
  2. @dylanahsmith @karmi
  3. @karmi

    [TEST] Fix technically not-working test for "outer scope variables" i…

    …n boolean query unit test
    karmi committed Oct 28, 2011
  4. @karmi
  5. @ralph @karmi
  6. @karmi

    [TEST] Added unit and integration tests showcasing restricting facet …

    …results with filters
    
    ElasticSearch allows you to restrict results from facets with `facet_filter` DSL.
    See <http://www.elasticsearch.org/guide/reference/api/search/facets/index.html>,
    chapter "Filter":
    
    > All facets can be configured with an additional filter (explained in the Query DSL section),
    > which will further reduce the documents they execute on. For example:
    
        {
          "facets" : {
            "<FACET NAME>" : {
              "<FACET TYPE>" : {
                ...
              },
              "facet_filter" : {
                "term" : { "user" : "kimchy"}
              }
            }
          }
        }
    
    In karmi/retire@d1f89e6, we fixed the issue where options passed to facets (see tests within the commit)
    were not encoded properly. However, as a side-effect, passing options to the facet definition itself
    was effectively "broken".
    
    Note, you have to pass these options to the `facet` method, not add it to the facet definition. Example:
    
        facet 'category', :facet_filter => {:term => {:id => category_ids}} do
            terms 'category_ids', :size => 100
        end
    
    Closes #138. Thanks @aaronchi for digging around and discovering the misunderstanding.
    karmi committed Oct 28, 2011
  7. @karmi
Commits on Oct 24, 2011
  1. @karmi

    Release 0.3.8

    karmi committed Oct 24, 2011
  2. @ralph @karmi
  3. @jwood @karmi

    Added support for mapping options ("fields") [#130]

    ElasticSearch allows you to define many top level options ("fields" in ES parlance)
    for a specific document type, such as `_source`, `_all`, etc.
    
    You may use it for [compressing the source](http://www.elasticsearch.org/guide/reference/mapping/source-field.html)
    (`"_source" : {"compress" : true}`), or for disabling the ES-specific
    [`_all` field](http://www.elasticsearch.org/guide/reference/mapping/all-field.html):
    `"_all" : { "enabled" : false }`.
    
    These options are passed as a Hash to the mapping method:
    
        class Article
          # ...
          mapping :_source => { :compress => true } do
            indexes :id,    :type => 'string',  :index    => :not_analyzed
            indexes :title, :type => 'string',  :analyzer => 'snowball',   :boost => 100
            # ...
          end
        end
    
    Closes #130.
    jwood committed with karmi Oct 18, 2011
Commits on Oct 21, 2011
  1. @karmi
Commits on Oct 20, 2011
  1. @mlitwiniuk @karmi

    [FIX] Fixed an error where `ZeroDivisionError` exception was raised f…

    …or empty result set
    
    Closes #110.
    mlitwiniuk committed with karmi Oct 20, 2011
Commits on Oct 19, 2011
  1. @karmi

    Release 0.3.7

    karmi committed Oct 19, 2011
  2. @karmi

    [FIX] Removed SDoc because it breaks on current RDoc (3.11)

    TODO: Add back once the gems get compatible again.
    
    Closes #129
    karmi committed Oct 19, 2011
  3. @michaelklishin @karmi
  4. @karmi
Commits on Oct 18, 2011
  1. @karmi

    Cleaned up and solidified code from karmi/retire@5161450 (#127)

    * Moved `s.fields` properly within the if..else block. Everybody should use the `fields` method when doing block searches.
    * Be careful with [something], Array(something) is better
    * Added more tests
    
    Closes #127.
    karmi committed Oct 18, 2011
  2. @sakrafd @karmi

    Added ability to set returned `fields` from simple model searches (#127)

        Article.search('title:T*', { :fields => "id",
                                     :page => (params[:page] || 1),
                                     :per_page => (params[:per_page] || 1000)})
    
    This is a combination of 2 commits.
    
    * allow setting fields in query string search i.e:
    
    * adding a unit test for specifying a fields option in a query string search
    sakrafd committed with karmi Oct 14, 2011
  3. @karmi

    Release 0.3.6

    karmi committed Oct 18, 2011
  4. @karmi

    [FIX] Fixed a bug: `Results::Item` was referencing Ruby classes incor…

    …rectly within Rails
    
    * (Possibly incompatible) Ruby classes instead of Results::Item were instantiated in `Item.new`
    * Calling `Item#class` would break code when no Ruby class matching document `_type` was found.
    
    This was the reason for mysterious errors such as:
    
        NameError (uninitialized constant Webpage)
    
    You had to be inside Rails, you had to be lacking the corresponding class, or your model
    would be incompatible with the attributes passed to an initializer.
    
    All very probable scenarios. My apologies, gentlemen.
    
    Closes #77.
    karmi committed Oct 18, 2011
  5. @karmi

    Cleaned up code and test suite for the Analyze API support

    * Use ActiveSupport's `Hash#to_param` helper method, since we're pulling in AS via ActiveModel anyway
    * Better naming
    * More readable, relevant and robust unit tests for the feature
    
    Closes #124.
    karmi committed Oct 18, 2011
  6. @karmi

    Added support for the Analyze API (#124)

    See <http://www.elasticsearch.org/guide/reference/api/admin-indices-analyze.html>
    
    This is a combination of 2 commits.
    
    * add support for analyze api
    * add assertions for variants
    rubish committed with karmi Oct 12, 2011
  7. @karmi

    [FIX] Added unit tests for the "nested type" support

    Reverted changes to test suite from karmi/tire/8c9d1c7. A unit test is more appropriate.
    
    Changes to existing tests were not warranted, integration tests for the feature are really redundant.
    
    (@rubish: When you add features, *add* tests and fixtures, do not *modify* existing ones, please. :)
    
    Closes #123.
    karmi committed Oct 18, 2011
  8. @karmi

    Added support for "nested type" for MyModel.mapping (#123)

    This is a combination of 4 commits.
    
    * add mapping for nested documents in models
    * add passing tests to check nested calls to
    * add failing test cases to deonstrate no way to have mapping type nested
    * add support for craeting mapping type nested by passing options
    
    See <http://www.elasticsearch.org/guide/reference/mapping/nested-type.html>
    rubish committed with karmi Oct 12, 2011
Something went wrong with that request. Please try again.