-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
Gateway: add a custom endpoint to retrieve total object count #373
Comments
Change pkg/{server, minio}: custom endpoint to return total object count mentions this issue. |
Is there any reason we decided not to add something to the satellite API instead of going through gateway with ListObjects calls? I may be missing some context, but just looking at the gateway change it seems like calling ListObjects might not be an efficient way of doing it. BTW: it would be helpful if background info is added to the issue and the commit message to aid in reviewing. |
Change pkg/{server, minio}: custom endpoint to return total object count mentions this issue. |
@halkyon - The context is in storj/storj#6080 (added to description as well) |
@ferristocrat Unfortunately it doesn't have everything, there's at least a couple of Slack threads with more details I had to go hunt down. Part of my problem generally is our reliance on Slack too much (it's horrible as a documentation source, and it's exclusive to open source contributions), but that's for another discussion ;) Anyway, judging by some discussions there's still some work to figure out what to do on this. |
GitHub Thread discussing options: https://storj.slack.com/archives/CAQV0AE2Z/p1698676617000929 |
11/19/24 @ferristocrat is this ticket still needed? |
The endpoint should return values for:
It should also be limited in some way (e.g. if there are 10s of millions of objects). Add a config value.
See "list buckets with attribution" for an example of a custom endpoint on gateway: https://github.com/storj/gateway-mt/blob/267c4fc8f7fdbb1953a8636ea305368a503d5506/pkg/minio/api-response.go#L25
Context for underlying issue: storj/storj#6080
AC:
The text was updated successfully, but these errors were encountered: