You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Robert Newson (JIRA)" <ji...@apache.org> on 2016/03/26 13:56:25 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=15212994#comment-15212994 ]
Robert Newson commented on COUCHDB-2849:
----------------------------------------
Can we change this from Blocker? As noted, each copy of each shard will have its own update_seq. While we _could_ include the packed sequences we use in _changes feeds (the base64 encoded output of term_to_binary of the {range, node, update_seq} tuples), it's unlikely to be of use to users.
> [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)