Currently there is no way of managing an online archive besides nuking the entire collection. This means that the collection can only grow, so costs will continue to climb.
The TTL index can already be used to automatically delete documents from your database. If this could be expanded to also delete files which have been archived, there is an easy and built-in way of maintaining an archive in size.4 votes
We'd like to have the ability to remove documents from an Online Archive. Mainly based on a date, but possibly other criteria.
We’re currently researching the best way to add support for this.
Currently to configure the online archive service, you specify which column you want to use, which must be a Date type. Our collections often use integer fields holding the offset from the epoch, and there are other fields people might reasonably used.
My suggsetion would be to allow for a diverse set of date types, or ideally, allow the user to specify the criteria themselves with a mongo query.4 votes
add more to the status of the online archive - for example, if I set it to 7days back it's good to know that currently at 80days.
An example: for a very big collection it takes long time to archive - so either show a % left until it caught up or show number of days currently at
other nice details: number of documents archived, archive rate, etc3 votes
Can you add support for storing the archive data in Azure Storage (instead of AWS S3 only), in a chosen by customer region (e.g. same region where the MongoDB cluster is running)?2 votes
I'd like to use Online Archive but I need to use Encryption Keys that my company manages, not ones provided by MongoDB.2 votes
We would like to see better compression for data stored in the Online Archive.
Data in our cluster is compressed very well using the WiredTiger storage engine.
Moving it out into the archive grows our data size by almost 4x.1 vote
- Don't see your idea?