On Thu, Mar 26, 2015 at 6:47 AM, Sai Asuka asuka.s...@gmail.com wrote:
telnet localhost:9300
should be
telnet localhost 9300
--
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,
'apply the filter before the query' doesn't make any sense to me - what
would it filter? I suspect I'm not really understanding you, can you tell
me more? Why do you want to be able to do this? How would it help?
anyway, from what I thing I do understand there are several ways to get the
results
The query as written will return a result because you are querying for
*Parent* documents that 'have children' matching your has_child query. You
can tell because the type in the url will be 'Foo'.
Hence, the filter you have specified is not run against the children, but
against the *parents*. In
, Perryn Fowler perryn.fow...@gmail.com wrote:
Further investigation shows that anything that makes use of _parent seems
to result in slow queries, be it has_parent, has_child or the 'children'
aggregation.
I should mention that I am using 1.4.4 - is this to be expected even
, Mar 2, 2015 at 12:23 PM, Perryn Fowler perryn.fow...@gmail.com
wrote:
Hello,
I am writing an analytics application that makes heavy use of aggregations.
My situation seems suited to parent/child. I have relatively few parents
(hundreds) and a lot more children (tens of millions
Hello,
I am writing an analytics application that makes heavy use of aggregations.
My situation seems suited to parent/child. I have relatively few parents
(hundreds) and a lot more children (tens of millions).
The has_parent query or filter provide an elegant way to perform the sort
of queries
You should be able to query the child type with a has_parent query which
has a has_child query nested within it.
No idea how it would perform though.
On Sun, Jan 25, 2015 at 3:29 AM, bvnrwork budda08n...@gmail.com wrote:
For example:
Have three below documents , FakeDoc,Doc1Doc2
Now how to
,
qbox.io ( Elasticsearch service provider http://qbox.io/)
On Tue, Jan 13, 2015 at 10:23 AM, Perryn Fowler perryn.fow...@gmail.com
wrote:
Hello,
I am building an application that performs aggregations over time-series
data.
The prevailing advice for my situation seems to be that I should use
Hello,
I am building an application that performs aggregations over time-series
data.
The prevailing advice for my situation seems to be that I should use
filters rather than queries to provide scope for my aggregations. The
reasons being
1) I have no need for scoring
2)
Hello
I have a use case that feels like a good fit for ElasticSearch except for
one problem. I'm hoping someone might be able to suggest an approach for
overcoming it using ElasticSearch.
I have a lot of time-series data from sensors. Extremely simplified, a
reading looks a bit like this
{
10 matches
Mail list logo
