[
https://issues.apache.org/jira/browse/COUCHDB-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375998#comment-15375998
]
Paul Joseph Davis commented on COUCHDB-2791:
--------------------------------------------
Initial implementation seems to be working well enough. I've tested db info,
single doc ops, _all_docs, _changes, and basic views. I've disabled any sort of
write operation though as that would likely get a cluster into a very bad state
if a user wasn't being careful. We can investigate adding write ops when we
look at adding safety precautions in the storage engine.
All in all this change is rather small and I'm actually fairly happy with how
its turned out. Its only superficially tested at this point so there will need
to be more done there before we call it good. I only read enough between
chttpd/fabric/couch_db to hopefully get all return values consistent. However
its possible I missed some differences here and there.
Branches are up:
https://github.com/apache/couchdb-couch/compare/master...cloudant:2791-allow-shard-access-through-cluster-port
https://github.com/apache/couchdb-fabric/compare/master...cloudant:2791-allow-shard-access-through-cluster-port
https://github.com/apache/couchdb-chttpd/compare/master...cloudant:2791-allow-shard-access-through-cluster-port
Let me know what y'all think.
> 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)
