Could anyone list a use case where one would prefer to use expiration type as segment as opposed to load?
Cheers
Pankaj.
Expiration types define how granular the disposition of documents is.
Document expires each document as it reaches the expiration point.
Load expires each load when the last document in a specific load reaches the expiration point.
Segment expires an entire database table (10 million rows by default) when the last document in that database table (or 'segment') expires.
As you can imagine, document expiration takes a long time, as CMOD has to delete each row individually. Load expiration is a little faster, as it can delete a series of documents rather quickly. Segment expiration is fastest, because you just drop the whole database table, and POOF!, it's gone.
The problem is that if you aren't loading tens of millions of rows each month, segment expiration keeps old documents around longer than you'd like, because older documents have to wait for newer documents to expire before the table can be deleted.
And finally, you should generally use the default "Load" expiration type unless you have a REALLY good reason -- because it's required for features like Enhanced Retention Management, should you add them in the future.
Hope that helps!
-JD.
Excellent. I can't agree more! Thanks JD.