It could be more clear if you post debugQuery=true response. Anyway, you've
find a solution, it's great.
There is no a performance pitfall in nested queries (_query_).
On Fri, Jan 20, 2017 at 5:24 PM, Ivan Bianchi wrote:
> Hi Mikhail,
>
> thanks for the answer, although both of queries still are
Hi Mikhail,
thanks for the answer, although both of queries still are giving me the
same "*child query must only match non-parent docs*" IllegalState error, as
I understand it is still seeing the second clause (has_schedules:false) as
part of the child filter.
Even using the v parameter inside th
It's my pet peeve. Try
?q={!parent which=content_type:activity}(schedule.weekday:1) OR
has_schedules:false&debugQuery=true
vs
?q= {!parent which=content_type:activity}(schedule.weekday:1) OR
has_schedules:false&debugQuery=true
and you'll see how space matters.
The pro's way is to
?q={!parent which
I hope someone can help me because I have spent too many time looking for
this issue :(
I have 2 kind of documents related with an 1-n relation, in my example this
is 1 activity has many schedules.
To achieve this I have some inner child document with schedule fields
inside the activity document.
