[
https://issues.apache.org/jira/browse/COUCHDB-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343013#comment-14343013
]
Alexander Shorin commented on COUCHDB-2537:
-------------------------------------------
Would like to close this as Won't Fix by following reasons:
1. CouchDB 2.0 isn't cluster only. It still may works in single node mode which
is like 1.x, but with more features. And the 1.x use cases are applicable here.
2. There are a lot of cases when knowledge about local_seq is useful. I'll add
one more: start listen changes feed from the point when the specific document
had been changed. Without knowing his seq that turns into iteration over whole
feed with not much of reasons.
3. It seems there are people who uses it. Removing ?local_seq=true will not
actually make our code simpler nor simplify API, but will only hide a part of
system information that could be useful in certain cases. In the end, this
parameter is optional.
What indeed worth to done is the return cluster wide seq (e.g. [1,"abcde"]
instead of just 1) on requesting document on cluster interface. But that's a
question for another issue.
> 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)
