Julie Tibshirani dc1856ca53 Make sure to validate the type before attempting to merge a new mapping. (#45157) ...

Currently, when adding a new mapping, we attempt to parse + merge it before
checking whether its top-level document type matches the existing type. So when
a user attempts to introduce a new mapping type, we may give a confusing error
message around merging instead of complaining that it's not possible to add
more than one type ("Rejecting mapping update to [my-index] as the final
mapping would have more than 1 type...").

This PR moves the type validation to the start of
`MetaDataMappingService#applyRequest` so that we make sure the type matches
before performing any mapper merging.

We already partially addressed this issue in #29316, but the tests there
focused on `MapperService` and did not catch this problem with end-to-end
mapping updates.

Addresses #43012.

2019-08-12 14:28:03 -07:00

..

licenses

Upgrade to Lucene 8.2.0 release (#44859) (#44892)

2019-07-26 08:14:59 +02:00

src

Make sure to validate the type before attempting to merge a new mapping. (#45157)

2019-08-12 14:28:03 -07:00

build.gradle

Upgrade HPPC to version 0.8.1 (#43025)

2019-06-12 13:14:16 +02:00