-
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
feat/add meta information consistency attribute #309
Conversation
Naming is from the issue, have no suggestion from my side. I do not like that attribute idea, cause it is more like a core feature for me, every container gonna have it and it changes the game significantly, but agree that an attribute thing makes it more flexible than a new field. |
252eb6b
to
ab48be9
Compare
Comments may be adjusted in the future when we will have more understanding of what the meta flow looks like. |
container/types.proto
Outdated
// * __NEOFS__METAINFO_CONSISTENCY \ | ||
// Policy rule that defines the condition under which an object is considered | ||
// processed. Acceptable values and meanings: | ||
// 1. <empty>/<missing attribute>: SN does not process objects' meta |
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.
attr value cannot be empty as stated above, absence is enough
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.
ok, reworded it to sound like "other cases" with the old behavior
container/types.proto
Outdated
// 2. "strict": SN processes objects' meta information, it is validated, | ||
// indexed and signed accordingly by a required minimal number of nodes | ||
// that are included in the container, a corresponding object inclusion | ||
// notification can be catch |
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.
// notification can be catch | |
// notification can be caught |
Closes #300. Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
ab48be9
to
a2baf6c
Compare
Closes #300.