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

Add support for single-file dataset representation in memory storage client #701

Open
vdusek opened this issue Nov 15, 2024 · 1 comment
Open

Add support for single-file dataset representation in memory storage client #701

vdusek opened this issue Nov 15, 2024 · 1 comment
Labels
t-tooling Issues with this label are in the ownership of the tooling team.

Comments

@vdusek
Copy link
Collaborator

vdusek commented Nov 15, 2024

  • Represent the dataset as a single file (or at least add an option for it) instead of a directory containing one file per item in the memory storage client.
  • There are already the export_to functions, which allow it. But that does not change the point that datasets are represented as file-per-item directories. So I would like to at least open it.
  • Definitely, further discussion should precede the implementation.
@vdusek vdusek added the t-tooling Issues with this label are in the ownership of the tooling team. label Nov 15, 2024
@janbuchar
Copy link
Collaborator

Also, this should probably be done after #92.

One more point - this makes sense for storage backends such as S3 where the client pays for each write.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@janbuchar @vdusek