Ability to define analyzer (and not tokenizers) in the parameter of the fulltext search. #57
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.
Elasticsearch is providing a lot of analyzers already ready for a lot of languages (italian, french,...) and we can easily define more analyzers in elasticsearch if we want to.
https://www.elastic.co/guide/en/elasticsearch/reference/6.2/analysis-lang-analyzer.html
But in the parameters of the fulltextSearch, we can only change the tokenizer and not the analyzer.
An analyzer (called "analyzer" in the code) is defined in the file lib/Service/IndexMappingService.php, in the method generateGlobalMap. This analyzer is used to analyze the content and the combined fields.
I believe it would be better to let the user define the analyzer (and not the tokenizer) in the parameters, and then use this user provided analyzer name for the analyze of the documents contents.
Warning :
So this PR is not a real PR. It is a kind of issue with a code example to make my issue clear...
Best regards,
Philippe