Support file bulk upload for frostfs-cli #1552
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1552
Loading…
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?
Is your feature request related to a problem? Please describe.
Sometimes I need to upload a bunch of files or directories into FrostFS Storage. To do that I have to run frostfs-cli in bash script.
Describe the solution you'd like
Consider having something like aws s3 sync command, that allows to synchronize selected files or directories. While it can delete files from storage as well, it would be nice to have at least bulk upload.
This new command can also provide both FilePath and FileName attributes.
Describe alternatives you've considered
Do nothing.
Additional context
For my demo, I needed to upload a bunch of video files so I modified
frostfs-cli object put
command to support dirs and wildcards, e.g.--file index*.ts
I would add a different command: it might have more parameters, related specifically to bulk upload. Not to clutter
object put
.That said, the problem is easily solved via external utils, so let's disscuss whether the supposed additional value is big enought to justify implementing this command.
Also it would be nice to have a bulk delete command in
frostfs-cli
. It can be useful to empty container or by a particular prefix after testing of bulk uploading, without having to recreate container or delete one-by-oneDo you suggest removing objects based on some search filter?
There are special cases here, like filtering
--user
objects, while also removing incomplete big object uploads.Yes, I mean deleting data, created by user with ability to filter. Maybe it can be done like in
find
command, where you can filter search result and specify action for each entry. Looks extensible for future needs