You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Alexander Shorin (JIRA)" <ji...@apache.org> on 2015/10/29 01:24:27 UTC
[jira] [Commented] (COUCHDB-2849) [2.0] update_seq option for
_all_docs view missing
[ https://issues.apache.org/jira/browse/COUCHDB-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979545#comment-14979545 ]
Alexander Shorin commented on COUCHDB-2849:
-------------------------------------------
I'm not sure that this would be possible to handle. At least for 2.0. And certainly, you won't be able to match update_seq with such easy since clusters have pretty cryptic and hardly predictable seqs. If you test cluster behind balancer then you'll have fun time because this update_seq will be different depending on the node you hit.
> [2.0] update_seq option for _all_docs view missing
> --------------------------------------------------
>
> Key: COUCHDB-2849
> URL: https://issues.apache.org/jira/browse/COUCHDB-2849
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Jan Lehnardt
> Priority: Blocker
> Fix For: 2.0.0
>
>
> While running the 1.x JS tests I found that _all_docs doesn’t support the update_seq option:
> ```
> resp = db.view('test/all_docs', {limit: 1, update_seq:true});
> T(resp.rows.length == 1);
> T(resp.update_seq == 101);
> ```
> resp.update_seq is undefined.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)