Skip to content
Commits on Mar 19, 2016
  1. @rjernst

    Revert "Build: Switch to maven-publish plugin"

    rjernst committed Mar 18, 2016
    This reverts commit a90a2b3.
Commits on Mar 18, 2016
  1. @jasontedor

    Merge pull request #17176 from jasontedor/its-not-easy-being-green

    jasontedor committed Mar 18, 2016
    Vagrant tests should be green
  2. @jasontedor
  3. @clintongormley

    Docs: Build release notes

    clintongormley committed Mar 18, 2016
  4. @clintongormley
  5. @clintongormley
  6. @jasontedor
  7. @s1monw

    Revert "Revert "Merge pull request #17182 from s1monw/issues/17090""

    s1monw committed Mar 18, 2016
    This reverts commit b693a52.
  8. @clintongormley
  9. @spinscale

    Docs: Display reindex/update by query API and fix build doc issue

    spinscale committed Mar 18, 2016
    The documentation existed, but was not linked anywhere.
    Also fixed the docs to make sure they build with this enabled.
  10. @s1monw

    Revert "Merge pull request #17182 from s1monw/issues/17090"

    s1monw committed Mar 18, 2016
    This reverts commit 0fe47f8, reversing
    changes made to 3b17ddc.
  11. @s1monw

    Merge pull request #17182 from s1monw/issues/17090

    s1monw committed Mar 18, 2016
    Provide better error message when an incompatible node connects to a node
    
    We should give a better exception message when an incompatible node connects
    and we receive a messeage. This commit adds a clear excpetion based on the
    protocol version received instead of throwing cryptic messages about not fully reaed
    buffer etc.
    
    Relates to #17090
  12. @martijnvg

    Removed old 1.x parent/child logic that should have been removed.

    martijnvg committed Mar 17, 2016
    `0` really means, don't match any child docs.
  13. @martijnvg
  14. @s1monw

    Provide better error message when an incompatible node connects to a …

    s1monw committed Mar 18, 2016
    …node
    
    We should give a better exception message when an incompatible node connects
    and we receive a messeage. This commit adds a clear excpetion based on the
    protocol version received instead of throwing cryptic messages about not fully reaed
    buffer etc.
    
    Relates to #17090
  15. @jasontedor
  16. @jasontedor
Commits on Mar 17, 2016
  1. @rjernst
  2. @jasontedor

    Fix plugins permissions

    jasontedor committed Mar 17, 2016
  3. @jasontedor
  4. @jasontedor
  5. @jasontedor
  6. @jasontedor

    Fix installed plugins check

    jasontedor committed Mar 16, 2016
  7. @jasontedor
  8. @jasontedor

    Add new plugins

    jasontedor committed Mar 16, 2016
  9. @jasontedor

    Add module tests

    jasontedor committed Mar 16, 2016
  10. @rjernst
  11. @rjernst

    Merge pull request #17128 from rjernst/maven_publish

    rjernst committed Mar 17, 2016
    Build: Switch to maven-publish plugin
  12. @polyfractal

    [TEST] Make test less fragile by sorting only on _uid

    polyfractal committed Mar 17, 2016
    The previous method sorted first by _score, then _uid.  In certain situations, this allowed
    floating point errors to slightly alter the sort order, causing test failure.
    
    We only sort on _uid now, which should be deterministic and allow comparison of ten
    documents.  Not quite as useful, but less fragile and we still check to make sure num hits
    and max score are identical.
    
    Closes #17164
  13. @jdconrad
  14. @bleskes

    Debug log on testMergesHappening

    bleskes committed Mar 17, 2016
  15. @martijnvg

    Merge pull request #17167 from martijnvg/parent_id_query_take_child_t…

    martijnvg committed Mar 17, 2016
    …ype_into_account
    
    parent_id query should take the child type into account too
  16. @martijnvg

    parent/child: `parent_id` query should take the child type into accou…

    martijnvg committed Mar 17, 2016
    …nt too.
    
    If this query doesn't take the child type into account then it can match other
    child document types pointing to the same parent type and that have the same id too.
  17. @s1monw

    Prevent index level setting from being configured on a node level

    s1monw committed Mar 14, 2016
    Today we allow to set all kinds of index level settings on the node level which
    is error prone and difficult to get right in a consistent manner.
    For instance if some analyzers are setup in a yaml config file some nodes might
    not have these analyzers and then index creation fails.
    
    Nevertheless, this change allows some selected settings to be specified on a node level
    for instance:
     * `index.codec` which is used in a hot/cold node architecture and it's value is really per node or per index
     * `index.store.fs.fs_lock` which is also dependent on the filesystem a node uses
    
    All other index level setting must be specified on the index level. For existing clusters the index must be closed
    and all settings must be updated via the API on each of the indices.
    
    Closes #16799
  18. @tlrx

    Fix OOM in AbstractXContentParser

    tlrx committed Dec 9, 2015
    This commit fixes an OOM error that happens when the XContentParser.readList() method is asked to parse a single value instead of an array. It fixes the UpdateRequest parsing as well as remove some leniency in the readList() method so that it expect to be in an array before parsing values.
    
    closes #15338
Something went wrong with that request. Please try again.