-
Notifications
You must be signed in to change notification settings - Fork 15
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
Tagging notifications in tree service #546
Labels
Comments
It seems it's one more case where we want to store |
May be useful for multipart upload (check) and for expiration in #192 (comment). |
Blocked the same as #533 (comment) |
Unblocked due to #536 (comment) |
masterSplinter01
pushed a commit
that referenced
this issue
Jul 20, 2022
Signed-off-by: Denis Kirillov <[email protected]>
Done in #598 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In tree service branch, we can't use
objInfo
structure in notifications like we do on master branch after bd5fd04. The reason is that object tagging does not involve operations in object service anymore.I have a couple proposals.
Do not use
data.ObjectInfo
inSendNotificationsParams
. Notification uses only a small subset of fields fromObjectInfo
: name, size, version, etag (hash). Those can be defined in a separate structure which can be built based onObjectInfo
or from scratch.Specify version in tagging notifications. Version is available in request. Without (1) we have to parse version into object.ID and then set it in
ObjectInfo
. After (1) we can set version string directly.Check what field actually need to be specified. In some notifications like delete notifications we avoid size and etag. I guess it is okay, but can we avoid this info in tagging notifications?
The text was updated successfully, but these errors were encountered: