Review Elasticsearch 8.0 Breaking Changes for potential issues
Anticipating the upcoming release of Elasticsearch 8.0 we will need to review the list of breaking changes and determine any testing that may be needed.
Elasticsearch has not published a release date for 8.0.
- If it's a possible concern we should list it here.
- We will take these issues and determine is we need to act on testing with the RC.
- because Gitlab 14.8 is releasing on Feb 22nd, Our changes that will be needed for compatibility would be in 14.9.
- We might determine the need to notify customers to not use Version 8.0 until Gitlab 14.x
https://docs.google.com/spreadsheets/d/1cZdajOyLUhRnotS3synkUJeQgVacy8KvKtfz-RdHJHY/edit?usp=sharing
-
Compile the full list in Google Sheets -
Review the list removing anything that can be clearly omitted -
Break the items left into 3 groups -
Add Notes for Each Item if it might be of concern -
Create Issues for Items that might be of concern for deep-dives -
Allocate time for the deep-dives - [ ] Add to Pipeline to test
Create issue for
Need to change from nGram
to ngram
located in Main Mapping Config.rb
ref breaking change
The nGram and edgeNGram tokenizer names have been removed.
The nGram and edgeNGram tokenizer names haven been deprecated with 7.6 and are no longer supported on new indices. Mappings for indices created after 7.6 will continue to work but emit a deprecation warning. The tokenizer name should be changed to the fully equivalent ngram or edge_ngram names for new indices and in index templates. Impact Use the ngram and edge_ngram tokenizers. Requests to create new indices using the nGram and edgeNGram tokenizer names will return an error."