# Too long values

**URL:** https://discuss.elastic.co/t/too-long-values/48884
**Category:** Elasticsearch
**Created:** [May 1, 2016, 9:11am UTC](https://discuss.elastic.co/t/too-long-values/48884 "2016-05-01T09:11:00Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Boris\_Borshevsky](https://avatars.discourse-cdn.com/v4/letter/b/71e660/32.png) [@Boris\_Borshevsky](https://discuss.elastic.co/u/Boris_Borshevsky)
#### Post date: [May 1, 2016, 9:11am UTC](https://discuss.elastic.co/t/too-long-values/48884/1 "2016-05-01T09:11:00Z")

</div>

Hi,  
I'm using elasticsearch 1.6.  
while trying to make an aggregation query I've noticed i have a pretty large glitch in my results, after some investigation, I've seen that when the of the aggregation is too long (not sure how long around 200-400 characters), the query just ignores it in the aggregation and still, counts it in the doc count.

Is there any fix or workaround for this issue?

---

<div class="post-metadata">

### 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: [May 2, 2016, 9:21am UTC](https://discuss.elastic.co/t/too-long-values/48884/2 "2016-05-02T09:21:51Z")

</div>

Hi,  
can you post and example of your query along with what response you get and what you would expect as a response instead?

---

<div class="post-metadata">

### Author: ![Boris\_Borshevsky](https://avatars.discourse-cdn.com/v4/letter/b/71e660/32.png) [@Boris\_Borshevsky](https://discuss.elastic.co/u/Boris_Borshevsky)
#### Post date: [May 2, 2016, 11:01am UTC](https://discuss.elastic.co/t/too-long-values/48884/3 "2016-05-02T11:01:01Z")

</div>

Hi,  
I've recreated something similar on my local machine  
ive started a new index;  
posted the following data to [http://localhost:9200/test/testtype/2](http://localhost:9200/test/testtype/2) :

{"gtype":"test1", "content":"testtesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttest" }

then tried this query:  
GET /test/\_search  
{  
"size": 0,  
"aggs": {  
"agg1": {  
"terms": {  
"field": "content",  
"size": 3000,  
"order": {  
"\_count": "desc"  
}  
}  
}  
}  
}

and got this result:  
{  
"took": 4,  
"timed\_out": false,  
"\_shards": {  
"total": 5,  
"successful": 5,  
"failed": 0  
},  
"hits": {  
"total": 1,  
"max\_score": 0,  
"hits": []  
},  
"aggregations": {  
"agg1": {  
"doc\_count\_error\_upper\_bound": 0,  
"sum\_other\_doc\_count": 0,  
"buckets": [  
{  
"key": "sttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttest",  
"doc\_count": 1  
},  
{  
"key": "testtesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttes",  
"doc\_count": 1  
},  
{  
"key": "ttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttestte",  
"doc\_count": 1  
}  
]  
}  
}  
}

which doesn't make sence.

---

<div class="post-metadata">

### 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: [May 2, 2016, 11:43am UTC](https://discuss.elastic.co/t/too-long-values/48884/4 "2016-05-02T11:43:52Z")

</div>

Hi Boris,

thats a funky bug! I can reproduce this with ES 1.6, 1.7 and also 2.3.1. I might be missing something obvious but this looks so strange that I would ask you to open a github issue for this with the above reproduction.

---

<div class="post-metadata">

### 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: [May 2, 2016, 11:48am UTC](https://discuss.elastic.co/t/too-long-values/48884/5 "2016-05-02T11:48:13Z")

</div>

A well no bug, I found the problem. The Standard Analyzer that is used when you don't specify an explicit string mapping is the culprit: if you look at [https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-standard-analyzer.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-standard-analyzer.html) you can see that the parameter `max_token_length` will split your term at 255 characters by default. So for your long string you get several tokens that all go to different buckets.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:54pm UTC](https://discuss.elastic.co/t/too-long-values/48884/6 "2017-07-05T22:54:46Z")

</div>


