# Java REST client returning long value in Exponential **URL:** \ **Category:** Elasticsearch\ **Created:** [September 15, 2017, 12:46pm UTC](https://discuss.elastic.co/t/java-rest-client-returning-long-value-in-exponential/100681 "2017-09-15T12:46:00Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Paddy\_Mahadeva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paddy_mahadeva/32/44225_2.png) [@Paddy\_Mahadeva](https://discuss.elastic.co/u/Paddy_Mahadeva)\ **Post date:** [September 15, 2017, 12:46pm UTC](https://discuss.elastic.co/t/java-rest-client-returning-long-value-in-exponential/100681/1 "2017-09-15T12:46:00Z")
Hi, I am using java REST client of Elasticsearch. I have a requirement where i need to find the max value of a long field from all the documents in an Index. I ran a POST [http://localhost:9200/myIndex/myType/\_search?size=0](http://localhost:9200/myIndex/myType/_search?size=0) with body { "aggs" : {{ "took": 2, "timed\_out": false, "\_shards": { "total": 5, "successful": 5, "failed": 0 }, "hits": { "total": 995, "max\_score": 0, "hits": [] }, "aggregations": { "MYID": { "value": 1805130000005357060 } } } "MYID" : { "max" : { "field" : "MYID" } } } } I get the output, "aggregations" : { "MYID" : { "value" : 1.80513000000535706E18 } } How can I work around this? For now I worked around this using BigDecimal in my java code. Is there any smarter way to do it? ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [September 15, 2017, 6:02pm UTC](https://discuss.elastic.co/t/java-rest-client-returning-long-value-in-exponential/100681/2 "2017-09-15T18:02:14Z")
> [@Paddy\_Mahadeva](#): > > I get the output, > > "aggregations" : { > "MYID" : { > "value" : 1.80513000000535706E18 > } > } How do you get that output. Can you share the code you are using? ---
**Author:** ![Paddy\_Mahadeva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paddy_mahadeva/32/44225_2.png) [@Paddy\_Mahadeva](https://discuss.elastic.co/u/Paddy_Mahadeva)\ **Post date:** [September 16, 2017, 5:59am UTC](https://discuss.elastic.co/t/java-rest-client-returning-long-value-in-exponential/100681/3 "2017-09-16T05:59:01Z")
Hi @cbuescher I am using the following Java code to get the data. ``` HttpEntity httpEntity = new NStringEntity( requestJSON.toString(), ContentType.APPLICATION_JSON); response = restClient.performRequest(Constants.HTTP_METHOD_GET, queryString.toString(), Collections.singletonMap( FieldNameConstant.PRETTY, Boolean.TRUE.toString()), httpEntity); String responseBody = EntityUtils.toString(response.getEntity()); logger.info("response array ["+responseBody+"]"); JSONObject jsonResp = new JSONObject(responseBody); JSONObject jsonAgg = (JSONObject)jsonResp.get(FieldNameConstant.ES_AGGREGATIONS); JSONObject jsonValue = (JSONObject)jsonAgg.get(idFieldName); BigDecimal bigValue = jsonValue.getBigDecimal(FieldNameConstant.ES_VALUE); ``` I tried using big decimal, big integer and long. I am loosing precision in every case. Also, after I create a new document with the next number, when I run the max id query after that, I get the old max value again. ie. I run the max query in my first post I get 1805130000005357060. Now I create a new document with MYid as 1805130000005357061. Now when I run the max query again, I get 1805130000005357060. This is perplexing, not sure if this has anything to do with precision loss. This is happening when I test with POSTMAN also, So i guess it may not be an issue with the REST Client. But now the issue is how do I find the max value of the long field from all my documents? Thanks Paddy ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [September 25, 2017, 10:13am UTC](https://discuss.elastic.co/t/java-rest-client-returning-long-value-in-exponential/100681/4 "2017-09-25T10:13:52Z")
@Paddy_Mahadeva sorry for the long delay, your original analysis that this is not only an issue with the REST client is right. The problem is the max-aggregation: all aggregations internally use a double representation because it makes sense for things like sums etc... but for min/max and for very large values this can come at the cost of precision. Here is an [issue](https://github.com/elastic/elasticsearch/issues/9545) that discusses this problem. ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [September 25, 2017, 11:44am UTC](https://discuss.elastic.co/t/java-rest-client-returning-long-value-in-exponential/100681/5 "2017-09-25T11:44:58Z")
> [@Paddy\_Mahadeva](#): > > How can I work around this? One possible workaround could be to sort on the MYID field and retrieve only the topmost document: ```auto POST http://localhost:9200/test/t/_search { "size": 1, "sort": [ { "MYID": { "order": "desc" } } ] } ``` ```auto { [...] "hits": { "total": 1, "max_score": null, "hits": [ { "_index": "test", "_type": "t", "_id": "1", "_score": null, "_source": { "MYID": 1805130000005357061 }, "sort": [ 1805130000005357061 ] } ] } } ``` Does this work for your use case? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 23, 2017, 11:45am UTC](https://discuss.elastic.co/t/java-rest-client-returning-long-value-in-exponential/100681/6 "2017-10-23T11:45:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.