Importing 917MB of JSON data

@kevinadi
I’ve actually just tried it myself and I can confirm that it did indeed go through.

2022-03-23T19:39:36.317-0400    using write concern: &{majority false 0}
2022-03-23T19:39:36.317-0400    using 4 decoding workers
2022-03-23T19:39:36.317-0400    using 1 insert workers
2022-03-23T19:39:36.318-0400    will listen for SIGTERM, SIGINT, and SIGKILL
2022-03-23T19:39:37.044-0400    filesize: 520 bytes
2022-03-23T19:39:37.044-0400    using fields: 
2022-03-23T19:39:37.044-0400    connected to: mongodb+srv://[**REDACTED**]@cluster0.1zfo5.mongodb.net/election
2022-03-23T19:39:37.044-0400    ns: election.tweets_try
2022-03-23T19:39:37.078-0400    connected to node type: replset
2022-03-23T19:39:37.150-0400    2 document(s) imported successfully. 0 document(s) failed to import.

So I’m guessing it might be a size issue. Because the only difference now is that the main file has about (approx) 3.7M objects inside vs this which has only two…

the main subject of this post has been resolved by @steevej, which I am truly grateful for and to @kevinadi for putting on the right track in finally getting this solved.

3 Likes