mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-27 14:45:49 +03:00
[GH-ISSUE #671] Store objects as binary instead of JSON #118
Labels
No labels
bug
compatibility-issue
docker
documentation
enhancement
help wanted
needs information
pull-request
question
stale
unfortunate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-gcs-server#118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gaul on GitHub (Feb 2, 2022).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/671
Storing objects in binary more efficient than encoding as JSON which has high memory usage for large files. fake-gcs-server can store the metadata in extended attributes instead. References #669.
@fsouza commented on GitHub (Feb 2, 2022):
Yeah using JSON isn't great, specially when we're dealing with ranges. It also means we can't store metadata for buckets (as they're represented as simple folders). I wonder if using extended attributes will limit what kind of filesystem we can use (I haven't done this before, so I really don't know), but we can definitely explore it.
Alternatively we can always have a metadata file in some structured format, in addition with the actual content.