-
Notifications
You must be signed in to change notification settings - Fork 17
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
Plugin langdetect not working under ES 2.0 #7
Comments
OK, now I've seen the examples aren't working anymore, because of the changed "language.json". Searching for english should be done with "eng" instead of "en" ... |
Sorry. This change was not intended. But you can safely remove/clear language.json, it adds the possibility of changing the language code by configuration. |
I will try to find a solution for the |
How is the relation of this plugin bundle to the single langdetect plugin? Is the single langdetect plugin still alive? |
Sorry for the confusion. I forked once but forgot to sync the changes. Please be patient for a new release which will be synced (both standalone and bundle) |
Trying the langdetect example from README.md with ES-2.0.0-Beta1 I get no hits, but also no error message.
When I change the command for creating the mapping to:
curl -XPOST 'localhost:9200/test/article/_mapping' -d '
{
"article" : {
"properties" : {
"content" : { "type" : "langdetect", "store" : "yes" }
}
}
}
'
I get the following error
{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Mapping definition for [content] has unsupported parameters: [store : yes]"}],"type":"mapper_parsing_exception","reason":"Mapping definition for [content] has unsupported parameters: [store : yes]"},"status":400}
Do you have an idea what could be the problem?
The text was updated successfully, but these errors were encountered: