The Atmos objects do not inherit ACL from the group ACL that is set at a bucket level.
If there is no user ACL provided, the ACL is inherited from the x-emc-useracl header.
If there is no group ACL provided, the Read ACL is used by default.
GET /rest/objects does not support different response types with x-emc-accept. For example, text/plain is not supported.
Read, Write, and Delete ACLs work in ECS the same as Atmos.
POST /rest/objects supports the x-emc-object-id header to enable legacy (44 character) object Ids.
Atmos listable tags
Listable tags are special user-defined tags used to list or filter objects. For example, an application could enable the user to tag a group of illustrations (objects) with a tag like "Vacation2016". Later the application can respond to a query of "Vacation2016" by listing only the objects tagged with this listable tag.
Using the Atmos protocol with ECS, a user cannot delete or modify another user's listable tags. Under some conditions, this ability is enabled in native Atmos.
Listable tags are indexed in ECS, increasing the performance and scalability of the retrieval of tagged objects.
In ECS, the
EMC_TAGS metadata tag is used to persist listable tags. This tag name should not be used in user-defined metadata tags.
Object ID length
Support for the Atmos API in ECS expands the length of the object Id from 44 characters to 101 characters. Hence, when moving applications from Atmos to ECS you need to be aware that the object Id length will be different.
To create an object with the legacy 44 character Id length, you can use the x-emc-object-id header. This enables objects to be migrated to Atmos.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\