I would like to facet on a user defined "keyword" field, but I know that
high cardinality fields can cause high memory usage in elasticsearch.
- I see starting in 0.90 there is an indices.fielddata.cache.size
parameter. If this is bounded, will it prevent all OOM issues or if the
values for a single field can't fit in memory will it still cause an OOM?
- Also is it still true that all facet values are loaded into memory
upon facet execution? If so, what is the purpose of the fielddata filter?
Wouldn't the values filtered from memory need to be accessed on disk again
at some point anyways? Or the filtered values are simply excluded from
consideration during facet execution?
- I see some older posts mentioned memory inefficiencies for multi
valued fields. Is this still the case in 0.90?
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@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b8c03166-a72d-4053-9af0-6a69e3e30cfb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.