Glynn Bird created COUCHDB-2537:
-----------------------------------
Summary: Propose removal of ?local_seq=true from the GET /db/doc
API for CouchDB 2.0
Key: COUCHDB-2537
URL: https://issues.apache.org/jira/browse/COUCHDB-2537
Project: CouchDB
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Database Core
Reporter: Glynn Bird
Prior to CouchDB 2.0, a document could be fetched thus:
/db/8E795956?local_seq=true
{Code}
{ _id: '8E795956',
_rev: '1-4fffae881c4d89048cf9319c2ae021a1',
test: 'somestuff',
_local_seq: 1 }
{Code}
with the _local_seq being returned indicating 'Document’s sequence number in
current database'.
Post CouchDB2.0, this quantity makes little sense as it represents the local
sequence number within the shard.
I propose that
* ?local_seq=true is deprecated
* _local_seq is no longer returned in the response
* the documentation is updated accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
