Closed baier closed 3 years ago
A fix has been to add all the language analyzers to AnalyzerMappings and also to return "english" instead of null in GetLanguageAnalyzer. Just to be able to create the indexes.
However, I'm wondering if the package should perhaps use the "standard" analyzer in all cases where a language analyzer does not exist?
A fix has been to add all the language analyzers to AnalyzerMappings and also to return "english" instead of null in GetLanguageAnalyzer. Just to be able to create the indexes.
However, I'm wondering if the package should perhaps use the "standard" analyzer in all cases where a language analyzer does not exist?
I agree with audunru, that does seem like the most reasonable approach.
@baier @audunru Is there a current workaround for that?
@TopalovOleg If I remember it correctly, we initially triggered the creation of indices in the code (but of course it failed whenever someone pressed a button in the GUI), so I think we forked the repo, did a fix there, and just used the fork instead (because we couldn't wait for a fix). And I think the fix was what @audunru mentions in the comment above.
This is actually, what we are doing on our side also..
https://github.com/Epinova/Epinova.Elasticsearch/releases/tag/v11.7.3.167 Please let us know if it's not working properly.
This is the error message (see snippet below) we get when trying to create a new index by clicking the "Create / Update" button in ElasticSearchAdmin. From what we can tell, the exception is thrown because we have enabled samii (language code se), which doesn't have a language analyzer (and thus is not supported in your code base). When we then refresh the page, the index is added, but its status is 'Closed'. What is odd is that we previously have been able to add the index - and it has been kept open, but lately we haven't been able to at all. How can be enable support and create an open index for a uncommon language?