Add support for unencrypted object metadata #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the necessary changes for the searchable metadata feature:
encrypted_metadata
field (just as for paths), but it would cause existing clients to fail without a metadata encryption key. So it was more modification in the common repository, but more backwards compatible.usermeta
package that converts deeply structured JSON from/to serializable metadata. For compatibility reasons, deep metadata structures are supported in the application layer: metadata object{"s":"text","o":[1,2,3]"}
are sent asmap[string]string
in the form of{"s":"text","json:o":"[1,2,3]"}
. It is the responsibility of satellite and the client application to encode/decode these shallow JSONs using theusermeta
package.