Potential memory overhead of the "Term Lookup" mechanism

Hi Guys,

We're about to use the "Term Lookup" mechanism
to do a term filter potentially on a big amount of terms, let's say 5'000
terms containing each of them 20 characters.

To design the documents everything is clear but before starting using this
feature (which is a way to do a kind of minimalistic "join" between two
indexes), we do have a controversial discussion internally about the
potential memory overhead relating to the use of this mechanism. I just
have the feeling that the overhead won't be so important but don't have any
factual arguments.

Is there anyone knowing how to approximate the memory which might be
consumed by this mechanism ?


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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/59e91c7f-e0a2-4402-a640-740911c322e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.