Extend objects to accept secondary metadata - Githubissues

storj / team-metainfo

GNU Affero General Public License v3.0

0 stars 0 forks source link

Extend objects to accept secondary metadata #71

Closed mniewrzal closed 2 years ago

mniewrzal commented 2 years ago

We have an issue with gateway-mt (https://github.com/storj/gateway-mt/issues/39) where metadata is not saved for MPU. Its a problem with our protocol as it doesn't allow to set metadata for object at the beginning of MPU upload. We agreed to fix it by extending object with secondary encrypted metadata which will be set with BeginObject request. Setting this secondary metadata will be exposed only for gateway-mt as a private method in storj/uplink. Both metadata will be sent while get/list to the client and on client side it will be decrypted and merged.

Metabase DB objects table needs to be extended with new columns:

secondary_encypted_metadata
secondary_encypted_metadata_encrypted_key
secondary_encypted_metadata_nonce

Replaced with https://github.com/storj/team-metainfo/milestone/2

storjBuildBot commented 2 years ago

Change https://review.dev.storj.io/c/storj/common/+/6629 mentions this issue.

mniewrzal commented 2 years ago

https://review.dev.storj.io/c/storj/storj/+/6624

Erikvv commented 2 years ago

Do we need tasks to change/validate move and copy?

mniewrzal commented 2 years ago

Do we need tasks to change/validate move and copy?

Good point. Added.

mniewrzal commented 2 years ago

I postponed it until server-side copy won't be implemented to avoid conflicts in code base.

storjBuildBot commented 2 years ago

Change https://review.dev.storj.io/c/storj/storj/+/6627 mentions this issue.