Daniel Mewes

@antoniocanas Another question: Does Horizon still come up in the end? If I'm not mistaken, the Horizon CLI retries connecting to the RethinkDB server a few times before giving up....

Something I didn't point out explicitly above: This can be used to implement both expiration after fixed TTL intervals or expiration based on a per-document TTL through the choice of...

I think I confused minimum and maximum. I edited the proposal (basically the timestamps in the index should represent the time at which a document should expire, so the older...

@mlucy > Is this going to be run in a single transaction? If so, that will be pretty high-latency. If not, I think this could get into an infinite loop...

@tatsujin1 > what would it look like "setting a flag on the document" as you mentioned? Yes, exactly what you wrote. In addition, you'll have to make sure that changing...

@marshall007 There's no technical limitation. Your usage example sounds reasonable, so I'm on board with allowing multiple of these. I'd like to think a bit more about the configuration API...

I actually don't like having expiration rolled into `indexCreate` very much, because from the user's point of view these are really different functionalities. An index is something you create to...

> Also, something to think about: at least one person is going to accidentally delete all their data by creating one of these on a `timestamp` index instead of a...

> A small nitpick, `expiration_offset` feels rather long and redundant, would `offset` suffice? Maybe. Are there any other good names for the argument? `delay` maybe?

In an offline discussion with @mlucy we thought that it might be nice to present expiration as an instance of "document eviction". An index+delay pair would be one type of...