[jira] [Commented] (COUCHDB-3336) r parameter for mango find in a cluster

["Jan Lehnardt (JIRA)" <ji...@apache.org>]

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

Jan Lehnardt commented on COUCHDB-3336:
---------------------------------------

Heya, like View reads, Mango reads are always r=1.

> r parameter for mango find in a cluster
> ---------------------------------------
>
>                 Key: COUCHDB-3336
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3336
>             Project: CouchDB
>          Issue Type: Documentation
>          Components: BigCouch, Documentation, Mango
>            Reporter: Bruno Michel
>
> It's not clear in the official documentation how mango indexes and searches are managed in a cluster of couchdb. From my experience, when inserting documents and then querying a mango index just after, there is a risk than a document doesn't appear in the index.
> The official documentation (http://docs.couchdb.org/en/2.0.0/api/database/find.html) doesn't say anything about the {{r}} parameter. But I've found its existence in https://github.com/apache/couchdb-mango#find. As I understand, even with {{r=3}}, there is no guarantee than a document that has just been inserted will be in the index (but if it is in the index, it will be the last version of its JSON content that will be answered).
> By the way, {{_explain}} has a surprising behavior for {{r}}. It is display like {{"r": [50]}}. I suppose it is an Erlang list of chars (50 is the ascii for '2').



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)