ElasticSearch user mapping: first name and last name should use a normalizer to allow case-insensitive sort #1259
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #1199
This pull request updates the Elasticsearch configuration in
openml_OS/libraries/ElasticSearch.phpto improve the indexing and search capabilities for user names. The main changes are the addition of new fields for first and last names with case-insensitive keyword indexing, and the introduction of a custom normalizer to ensure consistent lowercase storage and querying.Elasticsearch mapping improvements:
first_nameandlast_namefields to the mapping, both using thekeywordtype and alowercase_normalizerfor case-insensitive searches.Elasticsearch analysis configuration:
lowercase_normalizerin the index analysis settings, defined as a custom normalizer with a lowercase filter, to support the new case-insensitive keyword fields.