Re: Disabling key_as_string

Cracking, thanks Colin On Friday, August 1, 2014 3:28:45 PM UTC+1, Colin Goodheart-Smithe wrote: > > Sorry, I assumed you were using the histogram aggregation. It was this > aggregation that the fixed was applied to. I have opened issue #7125 >

Re: Disabling key_as_string

Sorry, I assumed you were using the histogram aggregation. It was this aggregation that the fixed was applied to. I have opened issue #7125 to resolve this in the terms aggregation. On Friday, 1 August 2014 14:04:52 UTC+1, James Grif

Re: Disabling key_as_string

Hi, I dug into that PR and it seems it was solved for histograms but not for terms aggregations. I presume this is a new bug, then? Are there other aggregation types this should be solved for? Thanks, James On Friday, August 1, 2014 2:04:52 PM UTC+1, James Griffin wrote: > > Hi Colin, > > T

Re: Disabling key_as_string

Hi Colin, Thanks for getting back to me so quick. I'm running my query against a 1.3.1 cluster and still seeing "key_as_string", even though no format parameter is in the query. My query is below: { "query": { "filtered": { "query": { "match_all": {} } } }, "a

Re: Disabling key_as_string

Hi James, This issue was brought up recently in the github issues list[1] and has been fixed[2]. It should be available in the version 1.3.0. [1] https://github.com/elasticsearch/elasticsearch/issues/6655 [2] https://github.com/elasticsearch/elasticsearch/pull/6830 Regards, Colin On Friday,

Disabling key_as_string

Hi, We're performing some aggregations with size=0 on a lot of data, and I'm looking to optimise the transfer over the wire. Our responses look like this: "buckets": [ - { - "key": 15, - "key_as_string": "15", - "doc_count": 8183 }, - { - "key": 100,