[
https://issues.apache.org/jira/browse/COUCHDB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914988#comment-13914988
]
ASF subversion and git services commented on COUCHDB-523:
---------------------------------------------------------
Commit 3015c8554ae38fc3fa7890209c5e394e5995e1c8 in couchdb-couch-mrview's
branch refs/heads/1993-bigcouch-couch-mrview from [~chewbranca]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-mrview.git;h=3015c85 ]
Add support for multi query views
This adds support for making multiple view queries in one request by
supplying a "queries" list in a POST request body. The primary
implementation was ported over from chttpd_view:multi_query_view/5.
The support added here is two fold. First, we add multi_query_view
support to the single node interface in couch_mrview_http. Second we
add support in couch_mrview_http:view_cb/2 to allow chttpd to utilize
this callback as well.
This also switches updates the #vacc record from setting a multi_query
flag, to instead setting a should_close flag. Now
couch_mrview_http:view_cb/2 will only start a new delayed response if
#vacc.resp is undefined, and similarly, it will only close a delayed
response if #vacc.should_close is true.
COUCHDB-523
COUCHDB-1993
> View API POST keys to retrieve multiple docs by key could also allow for
> multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... }
> params in the POST
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-523
> URL: https://issues.apache.org/jira/browse/COUCHDB-523
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
> Reporter: Nathan Stott
> Assignee: Russell Branca
> Priority: Minor
> Attachments: couch_httpd_view.erl, multi_start_end_key.diff,
> ranged_key_post.diff
>
>
> It would be useful if I could do a single POST to a view to retrieve multiple
> ranges specified by startkey, endkey.
> The format could be as follows:
> { "ranges": [ { "startkey": "a", "endkey": "c" }, { "startkey":"g",
> "endkey":"z" } ] }
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
