search

storj / gateway-st

Single-tenant, S3-compatible server to interact with the Storj network
Apache License 2.0
71 stars 19 forks source link

Enhancement: Metadata for files uploaded via native protocol #78

Open HAL9000COM opened 9 months ago

HAL9000COM commented 9 months ago

What did you do?

Upload files via Storj native protocol and access them via the gateway.

What did you expect to see?

Files should have metadata.

What did you see instead?

Files have no metadata.

Files uploaded via uplink cli or filezilla won't have metadata when accessed via the gateway, which have compatibility issue with S3 client (e.g. Nextcloud will always report "no ETag" error). I understand that Stroj native protocol does not upload metadata, but can this be solved by enhancement of the s3 gateway? Can such metadata be generated once accessed via the gateway, or some command that scan the bucket and create missing metadata? Related issue: #https://github.com/storj/storj/issues/5424

amwolff commented 7 months ago

I understand that Stroj native protocol does not upload metadata, but can this be solved by enhancement of the s3 gateway?

Objects uploaded through the gateway will have the necessary metadata. If you need S3-related metadata, it's best to use the gateway to upload them. Gateway-ST (this repository) has similar self-hosting capabilities to Uplink CLI.