Why not just use the --go-live option for MRIT and _put_ the data in
collectionB? Note this only works for Solr indexes that are hosted on
HDFS...

If your Solr collections are not on HDFS, then it's the same process
as I outlined. You create collectionB and copy things "to the right
place" after MRIT is done then alias, switching back and forth as
necessary.

The point is that you have two collections, the one currently serving
queries and the one getting indexed to. You go through whatever
process you need to completely rebuild the offline colleciton's index,
then alias.

Best,
Erick

On Fri, Mar 11, 2016 at 8:56 AM, praneethvarma
<itspraneethva...@gmail.com> wrote:
> Thank you Erick.
>
> I actually only have an index. I do not have collection B that hosts this
> index. The reducers of the MR job build an index (reducer per shard). I'm
> looking to load these generated lucene index files to the cores of a
> collection (new or existing and then I can work with aliasing after that as
> you suggested).
>
>
>
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/Load-pre-built-index-to-Solr-tp4263162p4263316.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to