# Terms Aggregation excluding last vowels using Spanish analyze - Elasticsearch 6.4 **URL:** \ **Category:** Elasticsearch\ **Created:** [August 7, 2019, 4:04am UTC](https://discuss.elastic.co/t/terms-aggregation-excluding-last-vowels-using-spanish-analyze-elasticsearch-6-4/194136 "2019-08-07T04:04:32Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![hcanales](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hcanales/32/51807_2.png) [@hcanales](https://discuss.elastic.co/u/hcanales)\ **Post date:** [August 7, 2019, 4:04am UTC](https://discuss.elastic.co/t/terms-aggregation-excluding-last-vowels-using-spanish-analyze-elasticsearch-6-4/194136/1 "2019-08-07T04:04:32Z")
I am trying to get keywords from a bunch of tweets in Spanish language. The thing is that when I get the results the last vowel in most words in the response is removed. Any idea of why is this happening? Here is the query: ``` { "query": { "bool": { "must": { "terms": { "full_text_sentiment": "positive" } }, "filter": { "range": { "created_at": { "gte": greaterThanTime, "lte": lessThanTime } } } } }, "aggs": { "keywords": { "terms": { "field": "full_text_clean", "size": 10} } } } ``` The mapping is the following for the field: ``` "full_text_clean": { "type": "text", "analyzer": "spanish", "fielddata": true, "fielddata_frequency_filter": { "min": 0.1, "max": 1.0, "min_segment_size": 10 }, "fields": { "keyword": { "type": "keyword", "ignore_above": 512 } } } ``` And this is the buckets in the response: ``` [ { key: 'aquí', doc_count: 3 }, { key: 'deport', doc_count: 3 }, { key: 'informacion', doc_count: 3 }, { key: '23', doc_count: 2 }, { key: 'corazon', doc_count: 2 }, { key: 'dios', doc_count: 2 }, { key: 'mexic', doc_count: 2 }, { key: 'mujer', doc_count: 2 }, { key: 'quier', doc_count: 2 }, { key: 'siempr', doc_count: 2 }] ``` where "deport", should be "deporte", "mexic" should be "mexico", "quier" should be "quiero" etc. Any idea of what is happening Thank you! ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 7, 2019, 7:13am UTC](https://discuss.elastic.co/t/terms-aggregation-excluding-last-vowels-using-spanish-analyze-elasticsearch-6-4/194136/2 "2019-08-07T07:13:21Z")
Hey, try using the [analyze API](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/indices-analyze.html#explain-analyze-api) with the spanish analyzer on some terms. The analyze API is doing the same steps that are done when a field of a document is split into terms and shows which terms are stored in the inverted index - as those are the ones that are also used in the aggregation response. I suppose the spanish analyzer is playing a role here. You might want to test with the standard analyzer for comparison. --Alex ---
**Author:** ![hcanales](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hcanales/32/51807_2.png) [@hcanales](https://discuss.elastic.co/u/hcanales)\ **Post date:** [August 7, 2019, 8:24pm UTC](https://discuss.elastic.co/t/terms-aggregation-excluding-last-vowels-using-spanish-analyze-elasticsearch-6-4/194136/3 "2019-08-07T20:24:30Z")
Hello Alexander, Thank you very much for your response. I already tried that and yes, it is because of the analyzer as I show below: This is the test request: ``` GET _analyze { "analyzer" : "spanish", "text" : "pero no puedo decir nada de deportes. Quiero que esto suceda en México" } ``` And this is the response: ``` "tokens": [ { "token": "pued", "start_offset": 8, "end_offset": 13, "type": "", "position": 2 }, { "token": "decir", "start_offset": 14, "end_offset": 19, "type": "", "position": 3 }, { "token": "deport", "start_offset": 28, "end_offset": 36, "type": "", "position": 6 }, { "token": "quier", "start_offset": 38, "end_offset": 44, "type": "", "position": 7 }, { "token": "suced", "start_offset": 54, "end_offset": 60, "type": "", "position": 10 }, { "token": "mexic", "start_offset": 64, "end_offset": 70, "type": "", "position": 12 } ] ``` It comes with the same issue. Any idea of how to solve it? I would like to keep using the analyzer in order to remove stop words, but with this issue, I cannot disseminate any functionality. -- Horacio ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [August 8, 2019, 9:39am UTC](https://discuss.elastic.co/t/terms-aggregation-excluding-last-vowels-using-spanish-analyze-elasticsearch-6-4/194136/4 "2019-08-08T09:39:12Z")
you could use a [stop analyzer](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/analysis-stop-analyzer.html) with your own custom set of stopwords or take a look at the [stop tokenfilter](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/analysis-stop-tokenfilter.html), which can be configured to use spanish stopwords. hope that helps. --Alex ---
**Author:** ![hcanales](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hcanales/32/51807_2.png) [@hcanales](https://discuss.elastic.co/u/hcanales)\ **Post date:** [August 12, 2019, 3:31pm UTC](https://discuss.elastic.co/t/terms-aggregation-excluding-last-vowels-using-spanish-analyze-elasticsearch-6-4/194136/5 "2019-08-12T15:31:20Z")
Turns out, that it is the stemmer in the Spanish analyzer, I just redefined and skipped the stemmer section ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 9, 2019, 3:31pm UTC](https://discuss.elastic.co/t/terms-aggregation-excluding-last-vowels-using-spanish-analyze-elasticsearch-6-4/194136/6 "2019-09-09T15:31:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.