-
Notifications
You must be signed in to change notification settings - Fork 472
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
feat(core): support user defined metadata for oss #4881
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM, thanks!
* 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_metadata
for metadatauser_metadata
for ossTodo: