8ac8c1f547
When creating a metadata mapper for a new type, we reuse an existing configuration from an existing type (if any) in order to avoid introducing conflicts. However this field type that is provided is considered as both an initial configuration and the default configuration. So at serialization time, we might only serialize the difference between the current configuration and this default configuration, which might be different to what is actually considered the default configuration. This does not cause bugs today because metadata mappers usually override the toXContent method and compare the current field type with Defaults.FIELD_TYPE instead of defaultFieldType() but I would still like to do this change to avoid future bugs. |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||