-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Mappings: Deprecate index_name and path #6677
Copy link
Copy link
Closed
Labels
:Search Foundations/MappingIndex mappings, including merging and defining field typesIndex mappings, including merging and defining field types>breakingTeam:Search FoundationsMeta label for the Search Foundations team in ElasticsearchMeta label for the Search Foundations team in Elasticsearchv2.0.0-beta1
Metadata
Metadata
Assignees
Labels
:Search Foundations/MappingIndex mappings, including merging and defining field typesIndex mappings, including merging and defining field types>breakingTeam:Search FoundationsMeta label for the Search Foundations team in ElasticsearchMeta label for the Search Foundations team in Elasticsearchv2.0.0-beta1
Type
Fields
Give feedbackNo fields configured for issues without a type.
Today we allow for custom index names. This adds ambiguity as fields might be referred to either according to their index name or their field name. What should happen when several fields have the same index name or if the index name of a field is the same as the full name of another field?
My understanding is that custom
index_names are not useful anymore now that we havecopy_toin order to index several logical fields into a single physical one, so I'd like to deprecate customindex_names so that the index name would always be the same as the full name.Relates to #4081, #8870