Question about Phrase Suggester's prefix_len


(Nik Everett) #1

According to
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters-phrase.htmlraising
prefix_len should improve performance and lowering it will make
things slower. If I set it to 0, is that really going to kill
performance? I've got someone complaining that "chokolade" doesn't correct
to "schokolade". As a someone who's highschool German faded long ago from
my memory I'd pronounce both words the same way.

Nik

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(simonw-2) #2

Nick I think you will suffer much from setting it to 0 but give it a try.
To do what you want to do have a second candidate generator that uses a
reverse filter with a reasonable prefix len?

simon

On Friday, October 18, 2013 4:05:15 PM UTC+2, Nikolas Everett wrote:

According to
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters-phrase.htmlraising prefix_len should improve performance and lowering it will make
things slower. If I set it to 0, is that really going to kill
performance? I've got someone complaining that "chokolade" doesn't correct
to "schokolade". As a someone who's highschool German faded long ago from
my memory I'd pronounce both words the same way.

Nik

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Nik Everett) #3

I'm not sure I'll get a chance to work on this soon but I'll remember to
try the reverse filters when I can. Is the goal of the prefix len just to
cut down on the number of candidates or to improve the locality of lookups
in the term statistics? Actually, I imagine both.

Thanks!

Nik

On Fri, Oct 18, 2013 at 3:00 PM, simonw
simon.willnauer@elasticsearch.comwrote:

Nick I think you will suffer much from setting it to 0 but give it a try.
To do what you want to do have a second candidate generator that uses a
reverse filter with a reasonable prefix len?

simon

On Friday, October 18, 2013 4:05:15 PM UTC+2, Nikolas Everett wrote:

According to http://www.elasticsearch.org/guide/en/elasticsearch/
reference/current/search-**suggesters-phrase.htmlhttp://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters-phrase.htmlraising prefix_len should improve performance and lowering it will make
things slower. If I set it to 0, is that really going to kill
performance? I've got someone complaining that "chokolade" doesn't correct
to "schokolade". As a someone who's highschool German faded long ago from
my memory I'd pronounce both words the same way.

Nik

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #4