Just Pushed: More routing goodness


(Shay Banon) #1

Hi,

I added (the last) feature that I wanted to get into 0.13 release, and

it extends the routing support added (
https://github.com/elasticsearch/elasticsearch/issues/closed#issue/470). The
following are the features added:

  1. Routing info is now stored automatically when indexing, and can be
    retrieved (in search/get) by specifying _routing in the fields section. This
    helps when wanting to reindex the data. Here is the issue:
    https://github.com/elasticsearch/elasticsearch/issues/closed#issue/515.
  2. Routing can be defined in the mapping as required, and indexing
    operations will fail if one is not provided. This is added as an extra safe
    mechanism to make sure a data is not indexed with specific routing. Issue:
    https://github.com/elasticsearch/elasticsearch/issues/closed#issue/520.
  3. When _routing is declared as required, a delete without explicit routing
    value gets broadcasted to the shards instead of hitting one (replication
    group). Issue:
    https://github.com/elasticsearch/elasticsearch/issues/closed#issue/522.
  4. A path can now be defined and the routing value can be automatically be
    extracted from an indexed document. Issue:
    https://github.com/elasticsearch/elasticsearch/issues/closed#issue/524.

-shay.banon


(medcl-2) #2

nice feature!!

On 11月17日, 下午11时54分, Shay Banon shay.ba...@elasticsearch.com wrote:

Hi,

I added (the last) feature that I wanted to get into 0.13 release, and

it extends the routing support added (https://github.com/elasticsearch/elasticsearch/issues/closed#issue/470). The
following are the features added:

  1. Routing info is now stored automatically when indexing, and can be
    retrieved (in search/get) by specifying _routing in the fields section. This
    helps when wanting to reindex the data. Here is the issue:https://github.com/elasticsearch/elasticsearch/issues/closed#issue/515.
  2. Routing can be defined in the mapping as required, and indexing
    operations will fail if one is not provided. This is added as an extra safe
    mechanism to make sure a data is not indexed with specific routing. Issue:https://github.com/elasticsearch/elasticsearch/issues/closed#issue/520.
  3. When _routing is declared as required, a delete without explicit routing
    value gets broadcasted to the shards instead of hitting one (replication
    group). Issue:https://github.com/elasticsearch/elasticsearch/issues/closed#issue/522.
  4. A path can now be defined and the routing value can be automatically be
    extracted from an indexed document. Issue:https://github.com/elasticsearch/elasticsearch/issues/closed#issue/524.

-shay.banon


(system) #3