# Exessive field mapping Twitter to Elasticsearch

**URL:** <https://discuss.elastic.co/t/exessive-field-mapping-twitter-to-elasticsearch/86401>\
**Category:** Logstash\
**Created:** [May 19, 2017, 10:08am UTC](https://discuss.elastic.co/t/exessive-field-mapping-twitter-to-elasticsearch/86401 "2017-05-19T10:08:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kubersakkie](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kubersakkie](https://discuss.elastic.co/u/kubersakkie)\
**Post date:** [May 19, 2017, 10:08am UTC](https://discuss.elastic.co/t/exessive-field-mapping-twitter-to-elasticsearch/86401/1 "2017-05-19T10:08:12Z")

</div>

Hey guys

I am using the ElasticStack\_twitter configuration to ingest tweets. (ES, Logstash and Kibana are on version 5.2)

[https://github.com/elastic/examples/tree/master/ElasticStack\_twitter](https://github.com/elastic/examples/tree/master/ElasticStack_twitter)

I have applied the exact same config and templates from this commit.

When I view the data in Kibana, it tells me that I have over 900 fields being indexed. This eventually fails with an error "more than 10000 fields in an index".

How would I only index the following related fields for any keyword searched:

created\_at  
id  
text  
source  
user  
geo  
coordinates  
place  
retweeted\_status  
retweet\_count  
favorite\_count  
favorited  
retweeted  
lang

Is this an elasticsearch mapping change or a Logstash filter change?

As always, thank you!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 19, 2017, 10:13am UTC](https://discuss.elastic.co/t/exessive-field-mapping-twitter-to-elasticsearch/86401/2 "2017-05-19T10:13:35Z")

</div>

You could try setting `full_tweet => false`.

---

<div class="post-metadata">

**Author:** ![kubersakkie](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kubersakkie](https://discuss.elastic.co/u/kubersakkie)\
**Post date:** [May 19, 2017, 10:22am UTC](https://discuss.elastic.co/t/exessive-field-mapping-twitter-to-elasticsearch/86401/3 "2017-05-19T10:22:11Z")

</div>

Hey @warkolm, tried that. Same result I'm afraid.

---

<div class="post-metadata">

**Author:** ![kubersakkie](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kubersakkie](https://discuss.elastic.co/u/kubersakkie)\
**Post date:** [May 19, 2017, 1:12pm UTC](https://discuss.elastic.co/t/exessive-field-mapping-twitter-to-elasticsearch/86401/4 "2017-05-19T13:12:34Z")

</div>

Found the problem.

When I edited the original github supplied ES template, I included a grievous typo.

Please consider this post closed and solved.

---

<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:** [June 16, 2017, 1:12pm UTC](https://discuss.elastic.co/t/exessive-field-mapping-twitter-to-elasticsearch/86401/5 "2017-06-16T13:12:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.