I created a large test collection with 152 million small documents, totalling 12.9GB. I used COMPASS to export it as JSON. The export ran and upon completion, COMPASS displayed a message stating it completed AND also dropped the collection itself (!!). Sadly, I did not grab a screen shot of the message. No error was displayed, and a collection.json document was created as expected (12.9GB in size).
I then imported the document into a new collection. The process ran for slightly longer than the export time... and completed to 100%. But only 15.1 million documents were created.
I suspect that it was the EXPORT side that failed, although it reached 100%.. Why it also dropped the source collection is a mystery. I have been unable to reproduce the issue, but will attempt to do so after the many hours spent creating the NOW LOST test data.
I will recreate the large dataset and attempt to reproduce on v1.24.6.
Export of large datasets should work fine.
Under no circumstances should the Compass Export process also DROP the source collection.
Import should fail if the import file is syntactically incorrect.
Documents were lost, likely during export. Import ran without any complaints. Does this mean the import file has all the closing syntax in place?
A screen shot of the approximate collection statistics prior to export is attached, along with the statistic after re-importing.
I can provide the export data file (12.9GB), if requested. It is all dummy data.