Feature #1451
Clean up ETags
| Status: | Closed | Start date: | 10/06/2011 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Antony Chazapis | % Done: | 100% |
|
| Category: | Pithos | Spent time: | - | |
| Target version: | - |
Description
We now store the ETag in the version's attributes - as the 'hash'. This can either be the MD5 or the Merkle hash of the object. When using PUT, as the whole data passes through, we compute the MD5. Updates trigger replacing the MD5 with the Merkle hash.
It has been proposed to return Merkle hashes independently (remove MD5 when updating), but does this introduce problems to OOS API clients when accessing objects with no MD5 recorded (no ETag)? Another option would be to always compute the MD5 sum after each update.
Associated revisions
Always include the Merkle hash in object meta (as returned from the backend). Clean up 'hash' references in frontend.
Needs database update.
Fixes #1451
Always include the Merkle hash in object meta (as returned from the backend). Clean up 'hash' references in frontend.
Needs database update.
Fixes #1451
History
#1 Updated by Antony Chazapis over 12 years ago
- Assignee set to Antony Chazapis
#2 Updated by Antony Chazapis over 12 years ago
- Target version changed from 0.8.1 to 0.7.10
#3 Updated by Antony Chazapis over 12 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset 4a1c29eac0deac20cf273b4e6ae375481074361b.
#4 Updated by Antony Chazapis over 12 years ago
It has been decided to keep the ETag code as is and to always return the Merkle hash. This way OOS clients will have a compatible ETag implementation, while Pithos-specific code can have the hashmap's hash without computing it. Producing the MD5 after each update should be avoided.
#5 Updated by Vangelis Koukis about 11 years ago
- Project changed from Pithos to Synnefo
- Target version deleted (
0.7.10)
#6 Updated by Vangelis Koukis about 11 years ago
- Category set to Pithos