Index page for FrostFS containers #151
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-http-gw#151
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.
In #137 we introduced index page for S3 buckets. S3 buckets store metadata in a tree service, so it is very convenient to iterate over object names, sizes and build tree.
However, index page will also be useful for FrostFS containers. FrostFS native protocol is more efficient to store raw objects. These objects may be accessed from HTTP Gateway, so listing of these objects will be useful.
Describe the solution you'd like
HTTP gateway should list all objects and efficiently receive all meta data about these objects ( probably some parallel HEAD requests?). Based on
FilePath
object attribute, it should create a directory tree and render it the same way as S3 Bucket index page.This is definitely may take some time to process in a large container. For now, consider simple implementation without any native protocol optimizations.
nzinkevich referenced this issue2024-10-11 13:46:59 +00:00
nzinkevich referenced this issue2024-12-02 08:48:50 +00:00