How to index a document with a ttl (time to live) associated with it?

[vantheshark]

Do we also need to prepare the TypeMappingProperty for _ttl?
Thanks

[Mpdreamz]

_ttl is not yet well supported in NEST. Will look into this asap.

[Mpdreamz]

@vanthoainguyen _ttl can now also be specified on IndexParameters. The Bulk() endpoint already supported this.

internal (i.e through mapping) ttl fields was also already supported.

[Mpdreamz]

associated commit: 655aef4

[mu-soliman]

According to Elasticsearch's documentation, The mapping should enable ttl, since it is disabled by default. Nest doesn't allow to specify ttl in mapping.

http://www.elasticsearch.org/guide/reference/mapping/ttl-field/

[ThomasArdal]

I'm having trouble getting ttl work with NEST as well. I specify TTL on the IndexParameters for the Index-method call, but the _ttl property is not set on the document. I think it's caused by the missing mapping of the ttl feature, as proposed by @muhammad-adel.

[Mpdreamz]

You can map the ttlfield with NEST see:

https://github.com/Mpdreamz/NEST/blob/master/src/Nest.Tests.Unit/Core/Map/FluentMappingFullExampleTests.cs#L84

[ThomasArdal]

Great. Any TTL attribute equivalent to the mapping api?

[Mpdreamz]

No sadly not, I'm mostly phasing out the attribute mapping for anything
more complex than field names, types, marking the id field.

You can easily swap an exisisting call to client.MapFromAttributes() call
with client.MapFluent(m=>m.MapFromAttributes()..ContinueHere)

That said I should look into supporting marking the TTL field from
attributes at least.

On Mon, Aug 12, 2013 at 12:25 PM, Thomas Ardal notifications@github.comwrote:

Great. Any TTL attribute equivalent to the mapping api?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/127#issuecomment-22484417
.

[ThomasArdal]

I'm planning to move over to MapFluent anyway. Phasing out attribute mapping makes total sense. Having two mapping strategies, always leaves one of them dangling, when adding new features.