{"action":"created","issue":{"url":"https://api.github.com/repos/olivere/elastic/issues/485","repository_url":"https://api.github.com/repos/olivere/elastic","labels_url":"https://api.github.com/repos/olivere/elastic/issues/485/labels{/name}","comments_url":"https://api.github.com/repos/olivere/elastic/issues/485/comments","events_url":"https://api.github.com/repos/olivere/elastic/issues/485/events","html_url":"https://github.com/olivere/elastic/issues/485","id":215537462,"number":485,"title":"Interval in Histogram Aggregation limited to integers?","user":{"login":"jgoodall","id":664213,"avatar_url":"https://avatars3.githubusercontent.com/u/664213?v=3","gravatar_id":"","url":"https://api.github.com/users/jgoodall","html_url":"https://github.com/jgoodall","followers_url":"https://api.github.com/users/jgoodall/followers","following_url":"https://api.github.com/users/jgoodall/following{/other_user}","gists_url":"https://api.github.com/users/jgoodall/gists{/gist_id}","starred_url":"https://api.github.com/users/jgoodall/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jgoodall/subscriptions","organizations_url":"https://api.github.com/users/jgoodall/orgs","repos_url":"https://api.github.com/users/jgoodall/repos","events_url":"https://api.github.com/users/jgoodall/events{/privacy}","received_events_url":"https://api.github.com/users/jgoodall/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-03-20T19:58:18Z","updated_at":"2017-03-26T10:36:08Z","closed_at":"2017-03-26T10:36:08Z","body":"The `Interval` field for histogram aggregations is currently limited to integers. The elasticsearch documentation says only that 'the interval must be a positive decimal' (https://www.elastic.co/guide/en/elasticsearch/reference/5.2/search-aggregations-bucket-histogram-aggregation.html), and using the HTTP API, floats work fine.\r\n\r\nIs there a reason that `interval` has to be an int? Would it work to make it an `interface` so it could take either an int or float?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/olivere/elastic/issues/comments/289271548","html_url":"https://github.com/olivere/elastic/issues/485#issuecomment-289271548","issue_url":"https://api.github.com/repos/olivere/elastic/issues/485","id":289271548,"user":{"login":"olivere","id":134848,"avatar_url":"https://avatars1.githubusercontent.com/u/134848?v=3","gravatar_id":"","url":"https://api.github.com/users/olivere","html_url":"https://github.com/olivere","followers_url":"https://api.github.com/users/olivere/followers","following_url":"https://api.github.com/users/olivere/following{/other_user}","gists_url":"https://api.github.com/users/olivere/gists{/gist_id}","starred_url":"https://api.github.com/users/olivere/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/olivere/subscriptions","organizations_url":"https://api.github.com/users/olivere/orgs","repos_url":"https://api.github.com/users/olivere/repos","events_url":"https://api.github.com/users/olivere/events{/privacy}","received_events_url":"https://api.github.com/users/olivere/received_events","type":"User","site_admin":false},"created_at":"2017-03-26T10:36:08Z","updated_at":"2017-03-26T10:36:08Z","body":"This change will be released in 5.0.32. Notice that some other fields in the histogram aggregation are also based on `float64` (e.g. min/max bounds and offset). So I changed them from `int64` to `float64` as well.\r\n\r\nYes, it's a breaking change. But it's easily changeable by users of elastic."}}
{"actor":{"display_login":"olivere"}}