I use my own framework and get already the top N results from a previous
processing.
I would like to use the aggregation framework of ES to use facets & co
features on such results.
I previously indexed my documents in ES.
What ES query should I do to avoid the scoring process and process only the
aggregation facets and co features using the IDs a set of documents as
query knowing that N could be large (N = 1K)?
One way to do it would be to store all those IDs in an Elasticsearch
document. Then, you can use the terms filter with the terms lookup
mechanism to have ES fetch all the terms for you:
As you can see there, you have quite a lot of options for caching.
I use my own framework and get already the top N results from a previous
processing.
I would like to use the aggregation framework of ES to use facets & co
features on such results.
I previously indexed my documents in ES.
What ES query should I do to avoid the scoring process and process only
the aggregation facets and co features using the IDs a set of documents as
query knowing that N could be large (N = 1K)?
I have a query from a user, run a process A returning a list of IDs
specific of the query and would like to use ES to enrich these ID with
aggregated info coming from the related (and already indexed) documents
so the list of IDs from the results are a prior unknown / depends on the
query of the user.
to use only the aggregation framework, you propose then for each query, to
first index the results of the process A (list of ID) as a lookup document.
and then after query ES using a term filter + lookup mechanism.
Is that right?
Le jeudi 24 avril 2014 13:40:22 UTC+2, Radu Gheorghe a écrit :
Hello,
One way to do it would be to store all those IDs in an Elasticsearch
document. Then, you can use the terms filter with the terms lookup
mechanism to have ES fetch all the terms for you:
On Thu, Apr 24, 2014 at 12:19 PM, NM <n.mais...@gmail.com <javascript:>>wrote:
Hi guys,
I use my own framework and get already the top N results from a previous
processing.
I would like to use the aggregation framework of ES to use facets & co
features on such results.
I previously indexed my documents in ES.
What ES query should I do to avoid the scoring process and process only
the aggregation facets and co features using the IDs a set of documents as
query knowing that N could be large (N = 1K)?
I have a query from a user, run a process A returning a list of IDs
specific of the query and would like to use ES to enrich these ID with
aggregated info coming from the related (and already indexed) documents
so the list of IDs from the results are a prior unknown / depends on the
query of the user.
to use only the aggregation framework, you propose then for each query, to
first index the results of the process A (list of ID) as a lookup document.
and then after query ES using a term filter + lookup mechanism.
Is that right?
Le jeudi 24 avril 2014 13:40:22 UTC+2, Radu Gheorghe a écrit :
Hello,
One way to do it would be to store all those IDs in an Elasticsearch
document. Then, you can use the terms filter with the terms lookup
mechanism to have ES fetch all the terms for you: Elasticsearch Platform — Find real-time answers at scale | Elastic
reference/current/query-dsl-terms-filter.html#_terms_lookup_mechanism
As you can see there, you have quite a lot of options for caching.
I use my own framework and get already the top N results from a
previous processing.
I would like to use the aggregation framework of ES to use facets & co
features on such results.
I previously indexed my documents in ES.
What ES query should I do to avoid the scoring process and process only
the aggregation facets and co features using the IDs a set of documents as
query knowing that N could be large (N = 1K)?
JAVA API
Thanks
--
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.