See
https://issues.apache.org/jira/browse/SOLR-4532
https://issues.apache.org/jira/browse/SOLR-1535
https://issues.apache.org/jira/browse/SOLR-4619
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Tue, Apr 16, 2013 at 7:37 AM, Furkan KAMACI wrote:
> Hi Erick;
>
> Thanks for the e
Hi Erick;
Thanks for the explanation. You said:
"You cannot transfer just the indexed form of a document from one
core to another, you have to re-index the doc." why do you think like that?
2013/4/16 Erick Erickson
> Yes. Every node is really self-contained. When you send a doc to a
> cluster
Yes. Every node is really self-contained. When you send a doc to a
cluster where each shard has a replica, the raw doc is sent to
each node of that shard and indexed independently.
About old docs, it's the same as Solr 3.6. Data associated with
docs stays around in the index until it's merged away
Hi Jack;
I see that SolrCloud makes everything automated. When I use SolrCloud is it
true that: there may be more than one computer responsible for indexing at
any time?
2013/4/15 Jack Krupansky
> There are no masters or slaves in SolrCloud - it's fully distributed. Some
> cluster nodes will be
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
There are no masters or slaves in SolrCloud - it's fully distributed. Some
cluster nodes will be "leaders" (of the shard on that node) at a given point
in time, but different nodes may be leaders at different points in time as
they become "elected".
In a distributed cluster you would never wan
