_suggest suggestion/question

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?

TIA
Lee

[1] http://www.elasticsearch.org/blog/you-complete-me/

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2367a474-f47b-43ae-bad0-7326256dec60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hello Lee ,

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?

TIA
Lee

[1] Elasticsearch Platform — Find real-time answers at scale | Elastic

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2367a474-f47b-43ae-bad0-7326256dec60%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/2367a474-f47b-43ae-bad0-7326256dec60%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGdPd5%3DeUSAokeXMu2kr49kQJqdX3v9ac4Lvb%3D-fvOh5VYKWhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Thank you, Vineeth.

On Sunday, August 17, 2014 12:04:20 PM UTC+1, vineeth mohan wrote:

Hello Lee ,

You will need to use context suggester for this purpose -
Elasticsearch Platform — Find real-time answers at scale | Elastic

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?

TIA
Lee

[1] Elasticsearch Platform — Find real-time answers at scale | Elastic

--
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:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2367a474-f47b-43ae-bad0-7326256dec60%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/2367a474-f47b-43ae-bad0-7326256dec60%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9ea51925-5ef8-48f3-8960-e5462e112713%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.