Comment 5 for bug 1365350
Revision history for this message
| Rajaneesh Singh (rajaneeshsingh1) wrote Re: Metadata constraints defined in openstack documents doen't match implementation | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Hi Christian,
The above case occurs in account and container only.
While in object case, the metadata is overwritten with new request's metadata. The old metadata is lost if we don't pass it in the new request.
There could be two possible ways to resolve this problem:
1. We can inherit the same behavior of metadata in case of account/container as of object i.e the metadata will be overwritten in every new request.
2. We can HEAD the account/container, then after confirming the constraints defined we can perform the required action:
* If the combined metadata(new+old) complies to the constraint values, we will process the request.
*If it doesn't comply to the constraints values, we will throw error.
Could you please suggest which solution would be better?