f the purpose for SolrCloud.
>> >>
>> >> Index transfer is automatic - SolrCloud supports fully distributed
>> update.
>> >>
>> >> You might be getting confused with the old "Master-Slave-Replication"
>> >> model that Solr h
> >> You might be getting confused with the old "Master-Slave-Replication"
> >> model that Solr had (and still has) which is distinct from SolrCloud.
> >>
> >> -- Jack Krupansky
> >>
> >> -Original Message- From: Furkan KAMACI
>
still has) which is distinct from SolrCloud.
>>
>> -- Jack Krupansky
>>
>> -----Original Message- From: Furkan KAMACI
>> Sent: Sunday, April 14, 2013 7:45 PM
>> To: solr-user@lucene.apache.org
>> Subject: Some Questions About Using Solr as Cloud
>&
hat Solr had (and still has) which is distinct from SolrCloud.
>
> -- Jack Krupansky
>
> -Original Message- From: Furkan KAMACI
> Sent: Sunday, April 14, 2013 7:45 PM
> To: solr-user@lucene.apache.org
> Subject: Some Questions About Using Solr as Cloud
>
>
> I re
5) When I use multi core design can I transfer one index data into another
core or anywhere else?
6) Does Solr holds old versions of documents or remove them?
2013/4/15 Furkan KAMACI
> I read wiki and reading SolrGuide of Lucidworks. However I want to clear
> something in my mind. Here are my qu
"Master-Slave-Replication" model
that Solr had (and still has) which is distinct from SolrCloud.
-- Jack Krupansky
-Original Message-
From: Furkan KAMACI
Sent: Sunday, April 14, 2013 7:45 PM
To: solr-user@lucene.apache.org
Subject: Some Questions About Using Solr as Cloud
I
I read wiki and reading SolrGuide of Lucidworks. However I want to clear
something in my mind. Here are my questions:
1) Does SolrCloud lets a multi master design (is there any document that I
can read about it)?
2) Let's assume that I use multiple cores i.e. core A and core B. Let's
assume that t
