Hi,
I want to use elastic search the following way:
On start up I want the Elastic Search to load all "my id fields" (one or
two small fields per document connecting between Lucene Doc Id and my
entities). The reason for that is I don't want to get Doc Id as a search
results and again make elastic search go to the disk to fetch me the "my id
fields" for documents found. Currently this is the way I work with Lucene
directly and I am pretty happy about it. Is there a way I can make elastic
search work the same way, in order to avoid another Lucene Db trip?
Elasticsearch 0.20.0 will have a warmup API that might help:
The issue does not go into much detail besides that it works with new
segments, but I am assuming it will populate the field caches as well.
If you have source enabled, Elasticsearch should retrieve the entire
resulting document in one call instead of a separate call for each field.
Not sure if source is retrieve during search however or if is still another
Lucene DB trip.
Cheers,
Ivan
On Sun, Sep 30, 2012 at 1:06 AM, Maxim Terletsky sxamt33@gmail.com wrote:
Hi,
I want to use Elasticsearch the following way:
On start up I want the Elastic Search to load all "my id fields" (one or
two small fields per document connecting between Lucene Doc Id and my
entities). The reason for that is I don't want to get Doc Id as a search
results and again make Elasticsearch go to the disk to fetch me the "my id
fields" for documents found. Currently this is the way I work with Lucene
directly and I am pretty happy about it. Is there a way I can make elastic
search work the same way, in order to avoid another Lucene Db trip?
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.