[
https://issues.apache.org/jira/browse/COUCHDB-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834675#comment-15834675
]
Garren Smith commented on COUCHDB-3276:
---------------------------------------
We changed the ETag to be an md5 of the document body. See here
https://issues.apache.org/jira/browse/COUCHDB-2978. We probably need to update
the documentation.
> ETag for local documents does not match _rev
> --------------------------------------------
>
> Key: COUCHDB-3276
> URL: https://issues.apache.org/jira/browse/COUCHDB-3276
> Project: CouchDB
> Issue Type: Documentation
> Components: HTTP Interface
> Reporter: Richard Ellis
>
> The ETag for _local documents in CouchDB 1.6.1 was the same as the document
> _rev field as is the usual case for documents. I think since
> https://issues.apache.org/jira/browse/COUCHDB-2978 the local documents now
> return an ETag that doesn't match the _rev field.
> The documentation at
> http://docs.couchdb.org/en/2.0.0/api/local.html#db-local-id for local
> documents still states that the "The semantics are identical to accessing a
> standard document in the specified database".
> I'm sure there is probably an argument for making the _local document _rev
> match the content based ETag, but at the very least the documentation needs
> to call out the difference in behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
