Just index two inputs, one with ü and one with ue. Alternatively you
replace ü to u as an analyzing/tokenization step (test it out, as your
mileage may vary).
No fixed date yet. Also no github ticket at the moment, sorry. I'll do
that soon (lacking a bit of time atm).
I am offering suggests for names ("firstname lastname"). Is it possible to
make suggestions also for "lastname firstname" WITHOUT using multiple
inputs? Can this be done also through the analyzers?
Thanks, joa
On Sunday, September 22, 2013 5:27:31 PM UTC+2, Alexander Reelsen wrote:
Hey,
Just index two inputs, one with ü and one with ue. Alternatively you
replace ü to u as an analyzing/tokenization step (test it out, as your
mileage may vary).
No fixed date yet. Also no github ticket at the moment, sorry. I'll do
that soon (lacking a bit of time atm).
--Alex
On Fri, Sep 20, 2013 at 5:13 PM, joa <joafe...@gmail.com <javascript:>>wrote:
Whats the best way to handle umlauts so that suggesting for "Otto
Mü..." and "Otto Mue..." lead to the same result?
When will the highlighting feature (approximately) be available? Is
there a ticket on github to follow?
Thanks!
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
I dont think so, at least nothing comes to my mind right now supporting
this. You could switch firstname lastname maybe using a pattern char
filter, but not both. Doing this before indexing seems like the way to go.
I am offering suggests for names ("firstname lastname"). Is it possible to
make suggestions also for "lastname firstname" WITHOUT using multiple
inputs? Can this be done also through the analyzers?
Thanks, joa
On Sunday, September 22, 2013 5:27:31 PM UTC+2, Alexander Reelsen wrote:
Hey,
Just index two inputs, one with ü and one with ue. Alternatively you
replace ü to u as an analyzing/tokenization step (test it out, as your
mileage may vary).
No fixed date yet. Also no github ticket at the moment, sorry. I'll do
that soon (lacking a bit of time atm).
Whats the best way to handle umlauts so that suggesting for "Otto
Mü..." and "Otto Mue..." lead to the same result?
When will the highlighting feature (approximately) be available? Is
there a ticket on github to follow?
Thanks!
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.