Skip to content

Remove possibility for conflicting field definitions and ambiguous field resolution #8870

Closed
@clintongormley

Description

@clintongormley

Fields with the same name in different types in the same index should have the same mapping. Previously, this has been advised as "best practice", but relying on advice has proved insufficient (see #4081 for the many issues that have resulted from allowing conflicting field definitions). Instead we need to enforce this in the API.

This issue (which replaces #4081) is a meta issue listing all of the changes that need to be made:

Alternatives:

  • Fields with different types can be renamed to distinguish their purpose, eg login_name vs login_date.
  • Different types can be separated into different indices.

Activity

63 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @clintongormley@timbunce@jordansissel@AshwinJay@gondar

        Issue actions

          Remove possibility for conflicting field definitions and ambiguous field resolution · Issue #8870 · elastic/elasticsearch