Inner_hits and highlighting

Elastic Stack Elasticsearch
1

Been playing with the new experimental inner_hits functionality released
in 1.5.0, mainly with child/parent related documents. It seems to work
really well but notice that highlighting doesn't seem supported on
content/fields within inner_hits; a quick scan of the code-base seems to
confirm this. Anyone know if this is already under consideration for a
future release?

Thanks, Ian.

--
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/6512722f-caa0-4f48-baf0-c255d8685cb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

If its not in the issues its unlikely that its planned. If it isn't planned
I think filing an issue is a good thing - just be super clear what you want
to do with examples in curl/gist form. If it is planned maybe add your
proposed usage to the issue.

Nik

On Tue, Apr 28, 2015 at 11:26 AM, Ian Battersby ian.battersby@gmail.com
wrote:

Been playing with the new experimental inner_hits functionality
released in 1.5.0, mainly with child/parent related documents. It seems to
work really well but notice that highlighting doesn't seem supported on
content/fields within inner_hits; a quick scan of the code-base seems to
confirm this. Anyone know if this is already under consideration for a
future release?

Thanks, Ian.

--
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/6512722f-caa0-4f48-baf0-c255d8685cb0%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/6512722f-caa0-4f48-baf0-c255d8685cb0%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/CAPmjWd2SdkCbZYdrjJE6PJ7TnF7Kce1ke0ZyuVpkVmVpgAW%3DUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

I think I've heard the ES team discourage the extensive use of this
aggregation type, mainly because it is highly expensive. Adding
highlighting support to it will more than double it's cost, and I'd
personally vote against it.

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Tue, Apr 28, 2015 at 8:17 PM, Nikolas Everett nik9000@gmail.com wrote:

If its not in the issues its unlikely that its planned. If it isn't
planned I think filing an issue is a good thing - just be super clear what
you want to do with examples in curl/gist form. If it is planned maybe add
your proposed usage to the issue.

Nik

On Tue, Apr 28, 2015 at 11:26 AM, Ian Battersby ian.battersby@gmail.com
wrote:

Been playing with the new experimental inner_hits functionality
released in 1.5.0, mainly with child/parent related documents. It seems to
work really well but notice that highlighting doesn't seem supported on
content/fields within inner_hits; a quick scan of the code-base seems to
confirm this. Anyone know if this is already under consideration for a
future release?

Thanks, Ian.

--
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/6512722f-caa0-4f48-baf0-c255d8685cb0%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/6512722f-caa0-4f48-baf0-c255d8685cb0%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/CAPmjWd2SdkCbZYdrjJE6PJ7TnF7Kce1ke0ZyuVpkVmVpgAW%3DUQ%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2SdkCbZYdrjJE6PJ7TnF7Kce1ke0ZyuVpkVmVpgAW%3DUQ%40mail.gmail.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/CAHTr4ZtRmigxAk8O-ZKp-cfQ9W5GOQ05Tk58knjcObLtUDLi_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.