copy is not a good choice, transfer to hdfs and merge.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Loading-an-index-generated-by-map-reduce-in-SolrCloud-tp4159530p4160855.html
Sent from the Solr - User mailing list archive at Nabble.com.
reload the
> > collection or core. Have not tried re-starting the solr cloud. Can
> someone
> > point out the best way to achieve the goal? I prefer not to re-start solr
> > cloud.
> >
> > Shushuai
> >
> >
> > ________________
>
gt; To: solr-user@lucene.apache.org
> Sent: Wednesday, September 17, 2014 6:53 PM
> Subject: Re: Loading an index (generated by map reduce) in SolrCloud
>
>
> FWIW, I do a lot of moving Lucene indexes around and as long as the core is
> unloaded it's never been an issue for So
solr cloud. Can someone
point out the best way to achieve the goal? I prefer not to re-start solr
cloud.
Shushuai
From: ralph tice
To: solr-user@lucene.apache.org
Sent: Wednesday, September 17, 2014 6:53 PM
Subject: Re: Loading an index (generated by map
FWIW, I do a lot of moving Lucene indexes around and as long as the core is
unloaded it's never been an issue for Solr to be running at the same time.
If you move a core into the correct hierarchy for a replica, you can call
the Collections API's CREATESHARD action with the appropriate params (mak
Details please. You say MapReduce. Is this the
MapReduceIndexerTool? If so, you can use
the --go-live option to auto-merge them. Your
Solr instances need to be running over HDFS
though.
If you don't have Solr running over HDFS, you can
just copy the results for each shard "to the right place".
Wha
