[COMPASS-3831] [Spike] Can we use mongoimport/mongoexport as the backend for the new Import/Export? Created: 16/Aug/19  Updated: 29/Oct/23  Resolved: 30/Aug/19

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: 1.21.0

Type: Investigation Priority: Major - P3
Reporter: Massimiliano Marcon Assignee: Lucas Hrabovsky (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: COMPASS-3013
Sprint: Iteration Llama

 Description   

This is a spike to understand whether we can use mongoimport/mongoexport as the backend of the new import/export.

Advantages:

  • They are widely used tools, they are stable and well maintained
  • By using them as a child process, we get them to run in the background out of the box
  • There is no difference in behavior between Compass and the CLI tools

Questions to answer:

  • can use mongoimport/mongoexport in a clean way inside electron?
  • what are the parameters that we need to pass to mongoimport/mongoexport? Are they easy to pass around in Compass?
  • Do we have a way to get progress information to display a progress bar inside Compass?
  • Can we easily get meaningful errors from the child process?
  • What happens if the child process crashes?

Generated at Wed Feb 07 22:34:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.