[
https://issues.apache.org/jira/browse/COUCHDB-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375345#comment-15375345
]
Paul Joseph Davis commented on COUCHDB-2791:
--------------------------------------------
I contemplated allowing writes and rejecting things but yeah, the level at
which we'd enforce that becomes the issue. I could easily add it in new HTTP
handlers I'll be adding but as you note it doesn't help anywhere else. But
adding this low enough means that we're tagging individual shards with an idea
of their shard range which would be the first time an individual shard has ever
known it was part of a cluster database. Which isn't a big deal, its just that
there's no current plumbing for that. I'm gonna start work on the read side and
will contemplate writes as I go, but I could see it happening after pluggable
storage engines land when we're starting to actually muck with the core storage
bits again.
> 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)
