One difference is that the store is compressed while the structure of the response that is built into memory is not (and potentially very wasteful).
The doc-by-doc comparison is done by the post-filter: for every document that matches the query, the filter is evaluated in order to know whether it matches or not. On the other hand, when a filter is in the query (either under a constant_score or a filtered_query), it can efficiently jump to the next matches using the inverted index. If you want to export your index, a more efficient way would be to use the `scan` search type: http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/scan-scroll.html. It basically opens a cursor that you can iterate on, as opposed as trying to get everything at once. On Fri, Nov 21, 2014 at 4:43 PM, Ajay Divakaran <[email protected]> wrote: > Each document has around 350 text fields. > > But im still not able to relate the store size to the memory spike. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/c8014753-b0e2-481c-85dc-8a9eceae7d32%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- Adrien Grand -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6jsKSLZFxkGgmw%2BQbmwr8WYyeWh_zqZWQOdX7Y4kivWA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
