-
Notifications
You must be signed in to change notification settings - Fork 8
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
special characters ñ or áéíóú and multi-word facets #11
Comments
Hi, sorry for delay - I was too busy with my job.
this is because elasticsearch recently released
doesn't metter |
I have the same problem with completion suggester. I have tried in many ways. I have checked with this way: Model user:
Model car:
This is my filter with facet
Once I'd made a search, I'd like to filter by the city of the vehicle owner. If I add my own mapping, Thanks! |
Ok I fixed the error with:
Thanks! |
I have a problem with special characters ñ or áéíóú.
my model:
This version works fine with special characters e.g.:
Query with
Martin
I get all results withMartín, martín, martin, Martin
With this approach this is the problem:
Now what results is individual words. e.g. A city tagged ["San Francisco", "Madrid"] will end up having three separate tags. Similarly, if I do a query to search on "san francisco" (must { term 'city', params[:city] }), that will fail, while a query on "San" or "Francisco" will succeed. The desired behaviour here is that the tag should be atomic, so only a "San Francisco" (or "Madrid") tag search should succeed.
To fix this problem I create my custom mapping:
With this mapping the problem with multi-words is fixed, and now facets with
city
field works fine:Instead of getting the type facets
San
andFrancisco
Now I getSan Francisco
Now, the problem is that with this mapping inside of the model the search doesn't find results with special characters e.g.:
Query with
Martin
I get only results withMartin martin
I'm using mongoid instead active record.
How can I fix this problem?
Thanks!
The text was updated successfully, but these errors were encountered: