Basically I have a parent document on which I collect all kind of dynamic
counters. Each counter has a name (which can be anything and is varied) and
a value.
I need to search based on name/value combination so the counters can't be
added as an array to the parent (otherwise searches will not bring correct
results). They can be either nested or children. Children seems more
appropriate as the parent document can be big and I don't want to re-index
it on every counter update (which can happen a lot).
I also have a set of predefined queries (which combine parent attributes
and counter values). When I index (update) a parent document I need to
check if it answers to one of the predefined queries.
On Tuesday, July 9, 2013 5:29:14 PM UTC+3, Boaz Leskes wrote:
Not that I can see. Perhaps if you tell me more about your application -
is the a chance of aggregated all the child document in the parent and
percolating it? Depending on the nuances of the query it may be inaccurate
but it might also be good enough for you.On Tue, Jul 9, 2013 at 4:21 PM, Rotem Hermon <rotem....@gmail.com<javascript:>
wrote:
No, the query will be a combination of parent / child attributes.
So if it's only near realtime the explain endpoint also doesn't fit my
use case. Is there any other way of doing this I might have missed?--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/jI0oU0BMsMU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.