Aggregations: Histogram Aggregation key Bug

[rnonnon-ebiz]

Hi,

I'm working with histogram aggregation but there is something strange with keys.
For instance (cf : http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations-bucket-histogram-aggregation.html):

If I use this request :

{
    "aggs" : {
        "prices" : {
            "histogram" : {
                "field" : "price",
                "interval" : 50
            }
        }
    }
}

I obtain something like this :

{
    "aggregations": {
        "prices" : {
            "buckets": [
                {
                    "key_as_string" : "0",
                    "key": 0,
                    "doc_count": 2
                },
                {
                    "key_as_string" : "50",
                    "key": 50,
                    "doc_count": 4
                },
                {
                    "key_as_string" : "150",
                    "key": 150,
                    "doc_count": 3
                }
            ]
        }
    }
}

Instead of :

{
    "aggregations": {
        "prices" : {
            "buckets": [
                {
                    "key": 0,
                    "doc_count": 2
                },
                {
                    "key": 50,
                    "doc_count": 4
                },
                {
                    "key": 150,
                    "doc_count": 3
                }
            ]
        }
    }
}

You could say, it's not important but it generates json ~1/3 bigger...
Is there a mean to disable this ???

Moreover, in Elasticsearch Java API, it could be fine to have a method to request the response as a hash instead keyed by the buckets keys (cf :http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations-bucket-histogram-aggregation.html#_response_format)

Thanks!!!

[jpountz]

There is currently no way to disable key_as_string.

Moreover, in Elasticsearch Java API, it could be fine to have a method to request the response as a hash instead keyed by the buckets keys

I am not sure to get what you mean. The Java API already has hash-like access to the buckets via the getBucketByKey method, is it what you are looking for?

[uboness]

this is a bug... the key_as_string should only be there if format is explicitly specified (like in all other aggs)

[rnonnon-ebiz]

Thanks jpountz for having format my post ;)
Thanks both for your answers.

I meant it's not possible to ask ES for a JSON like this :

{
    "aggregations": {
        "prices": {
            "buckets": {
                "0": {
                    "key": 0,
                    "doc_count": 2
                },
                "50": {
                    "key": 50,
                    "doc_count": 4
                },
                "150": {
                    "key": 150,
                    "doc_count": 3
                }
            }
        }
    }
}

Yes it's possible to access the Json with getBucketByKey but the JSON is like this :

{
    "aggregations": {
        "prices" : {
            "buckets": [
                {
                    "key_as_string" : "0",
                    "key": 0,
                    "doc_count": 2
                },
                {
                    "key_as_string" : "50",
                    "key": 50,
                    "doc_count": 4
                },
                {
                    "key_as_string" : "150",
                    "key": 150,
                    "doc_count": 3
                }
            ]
        }
    }
}

Furthermore if it's a bug, why close that post?

[clintongormley]

Furthermore if it's a bug, why close that post?

Because this post is still open, and the closed post is a duplicate.

[rnonnon-ebiz]

Oups... My Bad.... :s
Sorry