Arun, I think I was just confused. ES has a TTL capability using the _ttl field (which is why I was asking for your mapping). It "seems" like you are using a river that has may have its own "TTL" capabilities, outside of ES. The only thing I can tell you that is causing this error is that your river has field named _ttl of type string which conflicts with the built-in ES _ttl field. If you delete your index and rename that _ttl field in your river to something else, the error will likely go away. But I still don't know the answer to your original Q which is how do you enable TTL using this river. Unfortunately I'm not very familiar with this river to know the answer. :)
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/747ebe72-453b-4254-8f76-269d4b8fcd89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
