feat(core): support user defined metadata for oss#4881
Conversation
There was a problem hiding this comment.
the function comments in FutureWrite and other related structs are not unified and confusing.
for example:
- Set the append mode of op
- Set the content type of option
- Set the executor for this operation
Is the op, option, operation the same meaning ? shall we unify them ?
There was a problem hiding this comment.
Yes, they are the same. We can call them option. We can start a new PR for this.
Currently, none of the services that support blocking operations require user metadata. So, it seems there’s no need to support user metadata for the blocking operator, right? @Xuanwo |
I'm fine to split user metadata support of blocking operations into other PRs. Or just leave them not implemented. |
* feat(user_metadata): support user defined metadata for oss * fix cargo fmt && doc tests * Add user metadata key checks for oss && refeactor some code * remove unused code
part of: #4842
Done:
user_metadatafor metadatauser_metadatafor ossTodo: