Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support creating a compressed archive directly #32

Open
lewchuk opened this issue May 3, 2018 · 3 comments
Open

Support creating a compressed archive directly #32

lewchuk opened this issue May 3, 2018 · 3 comments

Comments

@lewchuk
Copy link

lewchuk commented May 3, 2018

The JSON files created by backup are highly compressible, especially if documents in a collection have similar fields. For my data a basic zip got ~70% compression. It would be great if the backup supported writing directly to a compressed archive to limit intermediate disk space.

@yoiang
Copy link
Member

yoiang commented May 4, 2018

Thinking out loud this makes sense to include in the tool vs recommending in people's workflow if it's a common usage we want to encourage. It makes complete sense to me, does anyone have a suggestion why this wouldn't?

@atlanteh
Copy link

Since this is a tool used mainly in scripts, I'd say it might be better to allow piping the data to another program rather than creating a specific zip with specific properties that people would probably like to change.
Please note that, if the DB size is bigger than available memory, then I'm not sure piping will work (and also zipping for that matter).

@atlanteh
Copy link

Since I was just told this tool uses multiple files, I think that piping will be a bit harder, so maybe the zip should be good enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants