Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Mappings: Allow to force dots in field names
With the changes in 5.0 to allow dots in field names for documents as well as mappings, we now have the possibility to allow a path forward for users which must have dots in fields on 2.x. This change adds an option to override the dot checks, `mapper.allow_dots_in_name` which may be set to `true` to omit the dots in field names error check. The resulting mappings will contain dots in the field names, and on upgrade to 5.x, those will be automatically converted to object mappings on startup. Note that this works because the underlying lucene indexes uses the full path. If a user users this to produce corrupt mappings, for example, two fields `foo` and `foo.bar` which are both text, the upgrade to 5.x will fail (because `foo` cannot be an object as well as a string field).
- Loading branch information