_routing in child type mapping prevents indexing

[kevingessner]

It appears that the child document's routing value is, by default, its parent's ID. Thus, if the parent has a _routing path set in its mapping, the child and parent will be mapped to different shards (which is bad).

Adding _routing to the child mapping does not help, as the value from the document does not override the default routing value (i.e. the parent's ID). Instead, it causes an exception while indexing the child document.

Reproduced in 0.19.0.RC3: https://gist.github.com/1902998

[kimchy]

Yea, at least for now you need to explicitly pass the routing value (which is a good practice if you can). It happens because setting the parent automatically set the routing value when indexing, so it does not go and tries to extract the routing value from the actual document.

[spinscale]

still the same behaviour with 1.2, quick reproduction with sense

DELETE test
PUT test

PUT /test/parent/_mapping
{
  "parent": {
    "_routing": {
      "required": true,
      "path": "account"
    }
  }
}

PUT /test/child/_mapping
{
  "child": {
    "_parent": {
      "type": "parent"
    },
    "_routing": {
      "required": true,
      "path": "account"
    }
  }
}

# error returned
PUT /test/child/c1?parent=p1
{
    "account": 1
}

# no error
PUT /test/child/c2?parent=p1&routing=1
{
    "account": 1
}

[clintongormley]

@spinscale perhaps close this in favour of #6730?

[spinscale]

if we decide to leave things as as they are now, this still needs to be fixed - and/or we could do it before 2.0 :-)

[clintongormley]

Closed in favour of #6730