"Lastly, it is not possible to “cross reference” between nested documents. One nested doc cannot “see” another nested doc’s properties. For example, you are not able to filter on “A.name” but facet on “B.age”. You can get around this by using `include_in_root`, which effectively copies the nested docs into the root, but this get’s you back to the problems of inner objects." http://www.elasticsearch.org/blog/managing-relations-inside-elasticsearch/
Perhaps this is our answer? On Friday, October 24, 2014 3:31:11 PM UTC-7, Zennet Wheatcroft wrote: > > I'm also running into this it is not what I expected. I tried parent/child > and got the same behavior. I expect the filtering to narrow down the > results with each filter. I filter on a child (or nested) that has > property=p then go back to aggregate on the parent and I get all the > results again as if the filter is not applied. > > I can include sample data, mapping, and queries if someone wants to > comment. > > I'm trying to do clickstream analysis on session events and user actions. > The data models I am trying are where the session is the parent event with > user actions as the child (or nested) events. I've tried several different > models and have not found one that works well. > > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/24b79787-aa22-4c15-8df1-831149d3f621%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
