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/28 21:00:29 UTC
[jira] [Commented] (COUCHDB-2857) Latest=true has no effect on
cluster
[ https://issues.apache.org/jira/browse/COUCHDB-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979136#comment-14979136 ]
Alexander Shorin commented on COUCHDB-2857:
-------------------------------------------
Well, actually latest=true has effect, but you interpreted it incorrectly.
Due to COUCHDB-2863 bug we return {"error":"unknown_error","reason":"function_clause","ref":162084788} here. Length property for objects returns undefined, undefined != 1, so assertion fails, but you eventually assumed and the reason was 2 != 1.
We need to move JS test suite on better framework to avoid such confusions.
> Latest=true has no effect on cluster
> ------------------------------------
>
> Key: COUCHDB-2857
> URL: https://issues.apache.org/jira/browse/COUCHDB-2857
> Project: CouchDB
> Issue Type: Bug
> Reporter: Sebastian Rothbucher
> Priority: Blocker
> Fix For: 2.0.0
>
>
> from basics.js integration test:
> var result = db.open("COUCHDB-954", {open_revs:[oldRev,newRev], latest:true});
> length of result is not 1 (for a doc with >1 revision)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)