Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
*Location*: http://docs.mongodb.org/manual/tutorial/expire-data/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.66 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/core/capped-collections/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: tutorial/expire-data
*Location*: http://docs.mongodb.org/manual/tutorial/expire-data/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.66 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/core/capped-collections/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: tutorial/expire-data
Description
db.log.events.ensureIndex(
{ "status": 1 },
{ expireAfterSeconds: 3600 })
Should warn users that this does not update an existing expiration index.
ie. Even if the 3600 is changed to 7200 for example, the index will still stay at the original 3600 unless the index is first removed.