-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Add pre-built named normalizers #53872
Copy link
Copy link
Closed
Labels
:Search Foundations/MappingIndex mappings, including merging and defining field typesIndex mappings, including merging and defining field types:Search Relevance/AnalysisHow text is split into tokensHow text is split into tokens>enhancementTeam:Search FoundationsMeta label for the Search Foundations team in ElasticsearchMeta label for the Search Foundations team in ElasticsearchTeam:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearch
Metadata
Metadata
Assignees
Labels
:Search Foundations/MappingIndex mappings, including merging and defining field typesIndex mappings, including merging and defining field types:Search Relevance/AnalysisHow text is split into tokensHow text is split into tokens>enhancementTeam:Search FoundationsMeta label for the Search Foundations team in ElasticsearchMeta label for the Search Foundations team in ElasticsearchTeam:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearch
Type
Fields
Give feedbackNo fields configured for issues without a type.
Like Analyzers, can we ship elasticsearch with some named defaults for normalizers?
One obvious example being "lowercase".
I'm not sure how we would handle any name-clashes with existing user-defined normalizers but it would make life simpler for users.
The new wildcard field is an example where making a field case insensitive is a common requirement. Ideally this would need a one-liner in the mapping rather than users having to mess with analysis settings and token filters.