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.

Sign up for GitHub

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

Jump to bottom

chore:Optimize S3 storage cost for AsyncToJson #21

Open
schadem opened this issue Jan 18, 2023 · 0 comments
Open

chore:Optimize S3 storage cost for AsyncToJson #21

schadem opened this issue Jan 18, 2023 · 0 comments
Labels
chore

Comments

@schadem
Copy link
Contributor

schadem commented Jan 18, 2023 •
edited
Loading

For a confident conversion of separate JSONs to a single JSON by AsyncToJson we should probably get rid of the original JSON file(s) i.e. 1, 2 etc. just to be frugal and save on S3 storage costs over-time, or at least provide flexibility to control it.
@schadem schadem added the chore label Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@schadem