[
https://issues.apache.org/jira/browse/SOLR-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144992#comment-14144992
]
Joel Bernstein commented on SOLR-6266:
--------------------------------------
Just did a quick review of:
https://github.com/couchbaselabs/couchbase-capi-server/blob/master/src/main/java/com/couchbase/capi/servlet/CAPIServlet.java
It appears the documents are not forwarded to other CAPIServers automatically.
They are just processed locally, so it is the responsibility of the bulkDocs
implementation to handle intra-cluster replication/routing.
So this appears to be the basic flow:
1) Couchbase sets up the initial replication and discovers the available
CAPIServers through the couchbase behavior api.
2) Couchbase replicates each document once across datacenter to one of the
available CAPIServers. (Still needs to be confirmed).
3) The local CAPIServer only forwards the docs to the bulkDocs implementation
If this scenario is correct, then we control the intra-cluster replication
ourselves, and we can run a CAPIServer on each replica without any issues.
> Couchbase plug-in for Solr
> --------------------------
>
> Key: SOLR-6266
> URL: https://issues.apache.org/jira/browse/SOLR-6266
> Project: Solr
> Issue Type: New Feature
> Reporter: Varun
> Assignee: Joel Bernstein
> Attachments: solr-couchbase-plugin.tar.gz,
> solr-couchbase-plugin.tar.gz
>
>
> It would be great if users could connect Couchbase and Solr so that updates
> to Couchbase can automatically flow to Solr. Couchbase provides some very
> nice API's which allow applications to mimic the behavior of a Couchbase
> server so that it can receive updates via Couchbase's normal cross data
> center replication (XDCR).
> One possible design for this is to create a CouchbaseLoader that extends
> ContentStreamLoader. This new loader would embed the couchbase api's that
> listen for incoming updates from couchbase, then marshal the couchbase
> updates into the normal Solr update process.
> Instead of marshaling couchbase updates into the normal Solr update process,
> we could also embed a SolrJ client to relay the request through the http
> interfaces. This may be necessary if we have to handle mapping couchbase
> "buckets" to Solr collections on the Solr side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
