Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Fri, 26 Sep 2014 16:02:34 +0000 (UTC)
From: "Karol Abramczyk (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12728741.1405987963000.132008.1411747354268@Atlassian.JIRA>
In-Reply-To: <JIRA.12728741.1405987963000@Atlassian.JIRA>
References: <JIRA.12728741.1405987963000@Atlassian.JIRA>
 <JIRA.12728741.1405987963627@arcas>
Subject: [jira] [Commented] (SOLR-6266) Couchbase plug-in for Solr
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Joel, Varun,

I fixed the code today to properly handle revsDiff and bulkDocs requests. It still runs only one CAPIServer per collection. I'm trying to implement automatic XDCR configuration via XDCR REST, but for unknown reasons I cannot create a remote cluster reference there. Usually I get response "Cluster uuid does not match the requested.". But I can get all remote clusters though. 

> 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-0.0.3-SNAPSHOT.tar.gz, 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org