[ 
https://issues.apache.org/jira/browse/SOLR-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143073#comment-14143073
 ] 

Karol Abramczyk commented on SOLR-6266:
---------------------------------------

Joel,

My plan was to collect Couchbase data with a single Solr shard leader (to start 
with) and let Solr replicate the data to the other replicas. I think that 
running CAPIServer on all replicas is pointless, as at the end they will send 
all received documents to the shard leader to index it. And this would cause 
increased network load because of the communication between Couchase servers 
and all the CAPIServers on replicas and also between the Solr replicas and Solr 
shards. I also wasn't sure if running CAPIServer on multiple replicas would 
result in indexing one document multiple times with different IDs. However, it 
could be useful to run CAPIServer on all shard leaders, but it would require 
the shard leader to calculate if the received document should be indexed in it. 

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to