-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orchard corrupts Elastic stemmer configuration #16384
Comments
Thank you for submitting your first issue, awesome! 🚀 We're thrilled to receive your input. If you haven't completed the template yet, please take a moment to do so. This ensures that we fully understand your feature request or bug report. A core team member will review your issue and get back to you. If you like Orchard Core, please star our repo and join our community channels. |
@Lenar-Avia I am not sure I follow your steps. But in order to create
Can you see if the above works for you? Here is a reference from our documentation |
Hello, dear! Also you ignore the fact that only "default" analyzer is working in OrchardCMS config |
Filters is not something we support in OC. Feel free to submit a PR that would add filters support in addition to the analyzers. |
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
Describe the bug
Customer Elastic analyzers configuration from OrchardCore_Elasticsearch block gets corrupt
Orchard Core version
1.8.2
To Reproduce
Steps to reproduce the behavior:
https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-lang-analyzer.html#spanish-analyzer
i.e. actual settings now do not contain "filter" area (on the same level as "analyzer")
Expected behavior
I would expect the termvectors to be created using stemmer.
When directly setting config using PUT ../_settings , custom morphological analyzer can be applied.
Logs and screenshots
Please try to reproduce the following settings using OrchardCore_Elasticsearch:
The text was updated successfully, but these errors were encountered: