My reading, which may not be accurate, of this [1] clear and concise post,
is that it is not possible to use a reference to an existing field as an
argument to a suggestor's 'input' or 'payload' fields.
Please would you clarify if I have missed something?
If I was correct, would it be much work to add these features?
You will need to use context suggester for this purpose -
Also this difference stems from the fact that , both actual data and auto
completion data are stored in different data structures.
This is to make sure that the auto completion data is memory resident and
thus super fast.
Thanks
Vineeth
On Sun, Aug 17, 2014 at 3:32 PM, Lee Gee leegee@gmail.com wrote:
My reading, which may not be accurate, of this [1] clear and concise post,
is that it is not possible to use a reference to an existing field as an
argument to a suggestor's 'input' or 'payload' fields.
Please would you clarify if I have missed something?
If I was correct, would it be much work to add these features?
Also this difference stems from the fact that , both actual data and auto
completion data are stored in different data structures.
This is to make sure that the auto completion data is memory resident and
thus super fast.
Thanks
Vineeth
On Sun, Aug 17, 2014 at 3:32 PM, Lee Gee <lee...@gmail.com <javascript:>>
wrote:
My reading, which may not be accurate, of this [1] clear and concise
post,
is that it is not possible to use a reference to an existing field as an
argument to a suggestor's 'input' or 'payload' fields.
Please would you clarify if I have missed something?
If I was correct, would it be much work to add these features?
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.