Re: Split child query to query and filter?

under the filtered-query *query *clause. בתאריך יום שלישי, 10 ביוני 2014 12:05:20 UTC+3, מאת Adam Porat: > > Hi, > > I need to perform a query + filter on child documents. For the query, > I'm using TopChildren. > Now I wonder what would be more efficient regarding

Re: Using facets/aggretagions on parent document, queried by TopChildren

I will answer myself: The facets are counted in relation to the total_hits in the response. This is true just as well when using TopChildren. בתאריך יום שלישי, 5 באוגוסט 2014 11:11:02 UTC+3, מאת Adam Porat: > > Hi, > >The TopChildren query works with an estimated hit s

Re: Index size on node VS heap size

7;t take > it, then you know the limit. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 12 August 2014 16:18, Adam Porat > > wrote: > >> Hi, >&

Index size on node VS heap size

Hi, Let's say my machine has 40G of RAM, and so I set HEAP_SIZE to 20G, as recommended. And let's say I have a single index on the machine. Rougly, how large can the index be to maintain good performance? Must it be somewhat less than 20G? Thank you. -- You received this message

Re: Nest - range filter in a form of BaseFilter

Any ideas anyone? בתאריך יום ראשון, 3 באוגוסט 2014 14:47:05 UTC+3, מאת Adam Porat: > > Hi, > I'm using Nest version 0.12.0. > I need to get a range filter in a form of BaseFilter. > However, this line of code creates a faulty BaseFilter which doesn't >

Using facets/aggretagions on parent document, queried by TopChildren

Hi, The TopChildren query works with an estimated hit size, and the TotalHits might be incorrect if there are more child docs matching the required hits. How does that affect facets or aggregations defined on the parent document? Would their count might be likewise be incorrent? Or would

Nest - range filter in a form of BaseFilter

Hi, I'm using Nest version 0.12.0. I need to get a range filter in a form of BaseFilter. However, this line of code creates a faulty BaseFilter which doesn't contain the actual condition: *agg.ElasticsearchFilter = Nest.Filter.Range(i => i.GreaterOrEquals(filteredUpdateDate));* Is this a bug, or

Re: Term aggregation/facet NOT INCLUDING the faceted field

: > > Hi Adam, you can do it today in a single query using post_filter, but it > is true that it is not very convenient. See discussion on > https://github.com/elasticsearch/elasticsearch/pull/7020 for more > information. > > > On Tue, Jul 29, 2014 at 11:32 AM, Adam Porat

Re: Term aggregation/facet NOT INCLUDING the faceted field

should look at post filters instead of adding filters to > the query. > > My 2 cents > > -- > David ;-) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 29 juil. 2014 à 11:32, Adam Porat > a > écrit : > > Hi, > > Faceted Navigation, as

Term aggregation/facet NOT INCLUDING the faceted field

Hi, Faceted Navigation, as can be seen in *LinkedIn *and *Booking.com*, include the fundamental characteristic that the value-count of each faceted field is constrained by the query (set of matched documents), *excluding *any constraint on the given field itself. For example, in Linke

Split child query to query and filter?

Hi, I need to perform a query + filter on child documents. For the query, I'm using TopChildren. Now I wonder what would be more efficient regarding query on *date/numeric (no score needed) fields* of this child - should I query on these fields using a HasChild filter in a bool query wit

Re: Maximum number of indices per machine

Hi Joerg & Itamar, Thanks for your reply. What I am trying to get is an order of magnitue. Suppose a server has 20GB RAM. Each index has about 20K documents, each document is about 500 words, average term distribution. The question is whether the server would be able to smoothly handle tenths, h

child documents - getting results & highlights of

Hi, Regarding has_child query, Is there a plan when will it will be possible to get the child document, as well as highlights? Thank you -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving em

Maximum number of indices per machine

Hi, How many *indices per machine* (roughly) can ElasticSearch handle smoothly? Let's say average # of documents per index is 20 thousand, and the machine is a powerful server. Thank you. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group