Ha! This is because raw:true adds more fields to the json doc.
Remove this option and see where it goes.
If you want to remove/add some fields, you can:
- do that in another process: means don't use twitter river
- use excludes in mapping. See: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-source-field.html#include-exclude
--
David 
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 13 déc. 2013 à 03:31, Finn Poitier finnpoitier@googlemail.com a écrit :
Thanks, David!
That works now insofar, that the river is actually using mymapping and doesn´t create another one called status.
But when starting the river, it automatically updates mymapping and adds all available properties from Twitter again. I guess that´s even intentional, maybe?
As result, the document size got an average of 3kb, while my goal was to reduce that to just the needed data.
Probably it makes sense to parse the tweet data into Redis and then using a Redis river to get it into ES?
Also chances, I´m still doing something wrong, as I just started with ES.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/84f9f244-93d4-4514-8483-375682e719d0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/81198451-7E1B-4910-83E2-5E22E0806314%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.