> > *Thanks for clarification.* > > *By default, it handles TTL cleanup once per minute (if I remember > correctly).* > > *If i'm not mistaken, Do you mean the record will be deleted & I should > not see the record when i search again after one minute of TTL. * >
After about 1 minute after the document has expired is when you should expect to see it deleted. This would mean (assuming default configurations and my memory is accurate) that if you configure 3m as the default TTL, then a document that is added with no TTL value will be expired after 3m and deleted after 4. > > *If the TTL value is negative I throw away the document as if it never > came back. A negative value only means that the document has expired but ES > hasn't yet run its cleanup to actually delete it.* > > *I don't see a TTL value returned in the response. so the TTL is not set ?* > I believe that you need to ask for the _ttl field to come back in the response. And in that case, you must also ask for _source since any explicit fields mean that _source won't be returned by default. > > > I set TTL as below - Not sure its correct. I'm using river JDBC. > I'm not sure. I push bulk updates though a BulkRequestBuilder. I don't like rivers they rarely all match up with the same version of ES that I am using; but my own Java code always matches up with the ES version I am using! Regards, Brian -- 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/f9b15d06-73a2-447b-a8f9-1a2d67610b40%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
