Unfortunately not for the completion suggester. The reason is because the
completion suggester uses an optimized data structure that is populated at
index-time. So you have to reindex your data (with the completion type) to
build that data structure.
this is currently not possible. From my experience, just adding arbitrary
suggestions with the same weight is not resulting in a good user
experience. Check out amazon for example, if you enter "iphone", the first
match is definately ranked in the suggestions, as this is not an iphone
case or the old iphone 3, but the most up to date one. This number might be
based on the selections for example, but it is rarely not ranked.
Will arbitrary non-ranked suggestions work in your case? (at the end of the
day, adding suggestions has two goals: Guiding the user faster to what he
most likely wants, and in addition maybe even offloading the search engine,
as suggestions might be more light-weight then queries).
I indeed do need to reindex from my river anyway. However, that field that
I want to use for completion suggester is also a field that is needed in
the primary index.
I suppose I could create a river from the single field using the "exclude"
fields feature of mongoriver....
Thoughts?
On Wednesday, April 16, 2014 9:16:02 AM UTC-5, Binh Ly wrote:
Unfortunately not for the completion suggester. The reason is because the
completion suggester uses an optimized data structure that is populated at
index-time. So you have to reindex your data (with the completion type) to
build that data structure.
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.