[jira] [Commented] (COUCHDB-2537) Propose removal of ?local_seq=true from the GET /db/doc API for CouchDB 2.0

["j ermouth (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303631#comment-14303631 ] 

j ermouth commented on COUCHDB-2537:
------------------------------------

But it still changes on doc save, and it’s the only value that is guaranteed to change.

Let’s imagine we save doc with _bulk_docs?new_edits=false – and overwrite some doc with another with absolutely same revision but other content. This situation is real in some scenarios.

Without _local_seq you won’t be able to determine that doc was changed in cases like above one.

And yes, CouchDB is not always cluster – in fact right now most of installations are not. I think same is correct for near future. 

So you can not assume no one use _local_seq – even if you think it’s meaningless. 

> 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)