And was curious if it is possible to get the BlockJoinCollector.getTopGroupssemantics using ElasticSearch. We have some really large documents due to
having a large number of children. If we could return only those children
that matched the nested query, that would save on post processing and IO
for ES. It would also allow use not have to store the source in certain
cases.
Just wondering if this is on the ES roadmap, and if so is there a github
issue I can track?
And was curious if it is possible to get theBlockJoinCollector.getTopGroupssemantics using Elasticsearch. We have some really large documents due to
having a large number of children. If we could return only those children
that matched the nested query, that would save on post processing and IO
for ES. It would also allow use not have to store the source in certain
cases.
Just wondering if this is on the ES roadmap, and if so is there a github
issue I can track?
And was curious if it is possible to get theBlockJoinCollector.getTopGroupssemantics using Elasticsearch. We have some really large documents due to
having a large number of children. If we could return only those children
that matched the nested query, that would save on post processing and IO
for ES. It would also allow use not have to store the source in certain
cases.
Just wondering if this is on the ES roadmap, and if so is there a github
issue I can track?
Thanks again!
Bob
--
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:>.
For more options, visit https://groups.google.com/groups/opt_out.
And was curious if it is possible to get theBlockJoinCollector.getTopGroupssemantics using Elasticsearch. We have some really large documents due to
having a large number of children. If we could return only those children
that matched the nested query, that would save on post processing and IO
for ES. It would also allow use not have to store the source in certain
cases.
Just wondering if this is on the ES roadmap, and if so is there a github
issue I can track?
Thanks again!
Bob
--
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:>.
For more options, visit https://groups.google.com/groups/opt_out.
That issue addresses what you have mentioned in your first email, but in
different wording. This issue it is on the roadmap, but there no concrete
short term plans to put this in a release.
And was curious if it is possible to get the BlockJoinCollector.**
getTopGroups semantics using Elasticsearch. We have some really large
documents due to having a large number of children. If we could return only
those children that matched the nested query, that would save on post
processing and IO for ES. It would also allow use not have to store the
source in certain cases.
Just wondering if this is on the ES roadmap, and if so is there a github
issue I can track?
Thanks again!
Bob
--
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.
Sorry Martin, I guess I misread the issue and thought it was already
closed. My mistake!
Cheers,
Bob
On Tuesday, 21 May 2013 07:30:14 UTC-4, Martijn v Groningen wrote:
Hey Bob,
That issue addresses what you have mentioned in your first email, but in
different wording. This issue it is on the roadmap, but there no concrete
short term plans to put this in a release.
Martijn
On 21 May 2013 01:14, btiernay <rtie...@gmail.com <javascript:>> wrote:
And was curious if it is possible to get the BlockJoinCollector.**
getTopGroups semantics using Elasticsearch. We have some really large
documents due to having a large number of children. If we could return only
those children that matched the nested query, that would save on post
processing and IO for ES. It would also allow use not have to store the
source in certain cases.
Just wondering if this is on the ES roadmap, and if so is there a
github issue I can track?
Thanks again!
Bob
--
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.
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.