Hi, ArangoDB's datafiles are written in an append-only fashion, meaning that delete/remove operations will simply add a "delete marker" to the datafiles. The datafiles are cleaned up eventually by a background compaction job.
arangodump will simply export the contents of a collection's datafiles, so the dump will also contain the "delete markers". This is not a problem, as replaying the dump from start to end allows to create the exact same state of data from the dump as has been present in the database at the point of the dump. arangorestore, the counterpart of arangodump, does exactly this. Please also note that the dump contains extra meta data about the documents that you probably don't need. If you're looking for a simple data export (export all active documents without additional meta data), there's also some good news: ArangoDB 3.2 will provide an arangoexport binary that will do exactly that. The binary is currently available in our devel branch only, but will become part of any proper 3.2 release. Best regards Jan Am Samstag, 11. Februar 2017 15:16:35 UTC+1 schrieb shahrouz sadeghi: > > Hi Guys, > > Could you please explain why arangodb keeps the deleted/modified records > in documents while getting dump from DB? and how we can clean the dump > files and get rid of deleted/modified records. Is there any specific > command/parameters. > > Regards, > Shahrouz > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
