[
https://issues.apache.org/jira/browse/COUCHDB-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375646#comment-15375646
]
Adam Kocoloski commented on COUCHDB-2791:
-----------------------------------------
Hmm ... we have a very clear and present use case for the parallelized access
to _changes. We know we can improve the throughput for data export by orders of
magnitude with this approach. What's the use case driving shard-level access
for the rest of the API?
I think designing the URL scheme to support a natural extension to other
operations makes sense, but I'd rather not expand the API surface area without
a demonstrated need to do so.
> Allow for direct parallel access to shards via _changes
> -------------------------------------------------------
>
> Key: COUCHDB-2791
> URL: https://issues.apache.org/jira/browse/COUCHDB-2791
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core
> Reporter: Tony Sun
> Assignee: Tony Sun
>
> For performance gains, we introduce a new _changes feed option parallel that
> returns a list of urls that the user can use to directly access individual
> shards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
