Hi Les
>From the release notes of
1.3.0(http://www.elasticsearch.org/downloads/1-3-0/), It does not mention
about the performance improvements to parent/child documents queries. I did
not find it 1.4.0(http://www.elasticsearch.org/downloads/1-4-0/) either.
How did you find that there are signi
Hi Ron.
Thanks a lot for the information. we are considering this plan for our
case.
Xiaolin.
On Wednesday, December 10, 2014 10:12:31 AM UTC-8, Ron Sher wrote:
>
> We had poor experience with has_parent queries and we ended up
> implementing it ourselves using 2 steps:
>
>1. Filter the p
We had poor experience with has_parent queries and we ended up implementing
it ourselves using 2 steps:
1. Filter the parent documents to get a list of IDs.
2. Filter the child documents and look only for IDs in the list of IDs
from 1
On Wednesday, December 10, 2014 7:48:55 PM UTC+2,
There is in fact a performance difference between has_parent and other
filters, as well as a difference in memory/cache use - especially in
earlier versions of ES. This is due to the way in which ES has to query the
parent/child relationship.
I do believe that there are some significant performanc
Hi David
Both queries return only 3 records. If I change the size to 10, the time
that the two queries take does not change . The first query still takes
about 100 milliseconds, and the second one still takes about 2000
milliseconds. Thanks a lot!
Xiaolin.
On Tuesday, December 9, 2014 10:53:
What happen if you change size to 10?
David
> Le 10 déc. 2014 à 03:53, Xiaolin Xie a écrit :
>
> Hi Elastic Search developers
>
> I am new to ES. We had some performance issues with our Elastic Search
> system, and we would like to get some ideas/thoughts about this issue from
> your guys.
>
Hi Elastic Search developers
I am new to ES. We had some performance issues with our Elastic Search
system, and we would like to get some ideas/thoughts about this issue from
your guys.
Here is our use case: we have three types of documents in one index:
“campaign_group”, “campaign”, and “a
