You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
routing as string looks to be baked in fairly deeply. So perhaps instead of supporting other types, like integers, a type error should be raised when mapping _routing path to a non-string field.
Heya, yea, it kindda expects the routing to be of type string, though, we should still be able to handle numeric values. Lemme check how we can fix that...
"_routing": { "required": true, "path":"customer_id" }
requirescustomer_id
to be a string.If the first document has an integer
customer_id
and no explicit field mapping, it'll raise a routing mismatch.If
customer_id
is explicitly mapped as an integer field, it always raises a routing mismatch.When
customer_id
is a string (whether implicitly in the first doc or explicitly in the mapping), it works.Repro at https://gist.github.com/1236728 on ES 0.17.7
The text was updated successfully, but these errors were encountered: