[
https://issues.apache.org/jira/browse/COUCHDB-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035729#comment-13035729
]
Paul Joseph Davis commented on COUCHDB-1170:
--------------------------------------------
I don't really have anything against show the checksum, though I might take md5
out of the name in case we ever decide to change the hash algorithm.
As to replication, do we short circuit attachment updates based on md5
somewhere? I haven't spent the time reading through the new replicator yet but
I would've thought I'd heard of that bit.
> include attachment md5 sums in _attachments
> -------------------------------------------
>
> Key: COUCHDB-1170
> URL: https://issues.apache.org/jira/browse/COUCHDB-1170
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 1.0.2
> Reporter: Randall Leeds
> Priority: Minor
> Fix For: 1.1
>
> Attachments: 0001-include-md5sum-field-in-_attachments-entries.patch
>
>
> Crucial to functioning replication is deterministic revisions. Attachment md5
> sums are used in CouchDB's revision generation (see couch_db:new_revid/1).
> Alternative CouchDB implementations may find it impossible or impractical to
> support binary attachments yet still wish to track changes and replicate
> efficiently with Apache CouchDB. To this end, such implementations need an
> efficient way to fetch all metadata necessary for calculating compatible
> revisions in the event of locally executed future updates.
> As a bonus, exposing this metadata is particularly beneficial for filesystem
> sync tools (such as couchapp implementations), e.g. through eliminating the
> need for redundantly storing checksums as user data on synchronized documents.
> To this end I propose the following 5-line patch which applies cleanly to
> trunk, 1.1.x and 1.0.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
