forked from TrueCloudLab/frostfs-api
[#50] *: Regenerate docs
Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com>
This commit is contained in:
parent
5602b8fa2a
commit
2a46a9ea0a
10 changed files with 118 additions and 301 deletions
|
@ -254,7 +254,7 @@ Statuses:
|
|||
#### Method Search
|
||||
|
||||
Search objects in container. Search query allows to match by Object
|
||||
Header's filed values. Please see the corresponding NeoFS Technical
|
||||
Header's filed values. Please see the corresponding FrostFS Technical
|
||||
Specification section for more details.
|
||||
|
||||
Extended headers can change `Search` behaviour:
|
||||
|
@ -404,16 +404,20 @@ been deleted;
|
|||
#### Method Patch
|
||||
|
||||
Patch the object. Request uses gRPC stream. First message must set
|
||||
the address of the object that is going to get patched. If the object's attributes
|
||||
are patched, then these attrubutes must be set only within the first stream message.
|
||||
the address of the object that is going to get patched. If the object's
|
||||
attributes are patched, then these attrubutes must be set only within the
|
||||
first stream message.
|
||||
|
||||
If the patch request is performed by NOT the object's owner but if the actor has the permission
|
||||
to perform the patch, then `OwnerID` of the object is changed. In this case the object's owner
|
||||
loses the object's ownership after the patch request is successfully done.
|
||||
If the patch request is performed by NOT the object's owner but if the
|
||||
actor has the permission to perform the patch, then `OwnerID` of the object
|
||||
is changed. In this case the object's owner loses the object's ownership
|
||||
after the patch request is successfully done.
|
||||
|
||||
As objects are content-addressable the patching causes new object ID generation for the patched object.
|
||||
This object id is set witihn `PatchResponse`. But the object id may remain unchanged in such cases:
|
||||
1. The chunk of the applying patch contains the same value as the object's payload within the same range;
|
||||
As objects are content-addressable the patching causes new object ID
|
||||
generation for the patched object. This object id is set witihn
|
||||
`PatchResponse`. But the object id may remain unchanged in such cases:
|
||||
1. The chunk of the applying patch contains the same value as the object's
|
||||
payload within the same range;
|
||||
2. The patch that reverts the changes applied by preceding patch;
|
||||
3. The application of the same patches for the object a few times.
|
||||
|
||||
|
@ -996,8 +1000,8 @@ prefix to the name. Here is the list of fields available via this prefix:
|
|||
* $Object:split.splitID \
|
||||
16 byte UUIDv4 used to identify the split object hierarchy parts
|
||||
* $Object:ec.parent \
|
||||
If the object is stored according to EC policy, then ec_parent attribute
|
||||
is set to return an id list of all related EC chunks.
|
||||
If the object is stored according to EC policy, then ec_parent
|
||||
attribute is set to return an id list of all related EC chunks.
|
||||
|
||||
There are some well-known filter aliases to match objects by certain
|
||||
properties:
|
||||
|
@ -1160,7 +1164,7 @@ And some well-known attributes used by applications only:
|
|||
MIME Content Type of object's payload
|
||||
|
||||
For detailed description of each well-known attribute please see the
|
||||
corresponding section in NeoFS Technical Specification.
|
||||
corresponding section in FrostFS Technical Specification.
|
||||
|
||||
|
||||
| Field | Type | Label | Description |
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue