Access parent properties from nested query

Elastic Stack Elasticsearch
1

Hi!

Is there any way to combine parent properties (e.g.
"publication_date") and nested-element properties (say,
"comments.content") in a single nested query (with path "comments", in
this case)? I know I could split the query in one nested part and
another non-nested one, but in my case this is not feasible, since I'm
working with rather complex, automatically generated queries. Is there
a way to do this inside a single nested query?

Thanks!

Felix

2

There isn't a way to do it, but, part of the work left for nested queries is
to automatically detected fields that refer to nested objects, and convert
them to nested queries, will that help in your case?

On Tue, Aug 2, 2011 at 4:13 PM, Felix Sappelt f.sappelt@clueda.com wrote:

Hi!

Is there any way to combine parent properties (e.g.
"publication_date") and nested-element properties (say,
"comments.content") in a single nested query (with path "comments", in
this case)? I know I could split the query in one nested part and
another non-nested one, but in my case this is not feasible, since I'm
working with rather complex, automatically generated queries. Is there
a way to do this inside a single nested query?

Thanks!

Felix

3

I dont think it would, but that's a nice feature nonetheless. I think
I'll just index all metadata with every nested object, that should
work. Thanks!

On Aug 2, 3:59 pm, Shay Banon kim...@gmail.com wrote:

There isn't a way to do it, but, part of the work left for nested queries is
to automatically detected fields that refer to nested objects, and convert
them to nested queries, will that help in your case?

On Tue, Aug 2, 2011 at 4:13 PM, Felix Sappelt f.sapp...@clueda.com wrote:

Hi!

Is there any way to combine parent properties (e.g.
"publication_date") and nested-element properties (say,
"comments.content") in a single nested query (with path "comments", in
this case)? I know I could split the query in one nested part and
another non-nested one, but in my case this is not feasible, since I'm
working with rather complex, automatically generated queries. Is there
a way to do this inside a single nested query?

Thanks!

Felix