So, am I following this correctly by saying that, this proposed solution would present us a way to index a collection on an offline/dev solr cloud instance and *move* that pre-prepared index to the production server using an alias/rename trick?
That seems like a reasonably doable solution. I also wonder how much work it is to build the shards programmatically (e.g. directly in a hadoop/java environment), cutting out the extra step of needing another solr instances running on a staging environment somewhere. Then using this technique to swap in the shards. I might do something like this first and then look into simplifying, and further automating, later on. And if it is indeed possible to build a hadoop driver for indexing, I think that would be a useful tool for the community at large. So I'm still curious about it, at least as a thought exercise, if nothing else. Thanks, Dave -----Original Message----- From: Furkan KAMACI [mailto:furkankam...@gmail.com] Sent: Monday, May 06, 2013 9:44 PM To: solr-user@lucene.apache.org Subject: Re: Indexing off of the production servers Hi Erick; Thanks for your answer. I have read that at somewhere: I believe "redirect" from replica to leader would happen only at index time, so a doc first gets indexed to leader and from there it's replicated to non-leader shards. Is that true? I want to make clear the things in my mind otherwise I want to ask a separate question about what happens for indexing and querying at SolrCloud. 2013/5/6 Shawn Heisey <s...@elyograg.org> > On 5/6/2013 7:55 AM, Andre Bois-Crettez wrote: > > Excellent idea ! > > And it is possible to use collection aliasing with the CREATEALIAS > > to make this transparent for the query side. > > > > ex. with 2 collections named : > > collection_1 > > collection_2 > > > > > /collections?action=CREATEALIAS&name=collectionalias&collections=colle > ction_1 > > > > "collectionalias" is now a virtual collection pointing to collection_1. > > > > Index on collection_2, then : > > > /collections?action=CREATEALIAS&name=collectionalias&collections=colle > ction_2 > > > > "collectionalias" now is an alias to collection_2. > > > > > http://wiki.apache.org/solr/SolrCloud#Managing_collections_via_the_Col > lections_API > > Awesome idea, Andre! I was wondering whether you might have to delete > the original alias before creating the new one, but a quick look at > the issue for collection aliasing shows that this isn't the case. > > https://issues.apache.org/jira/browse/SOLR-4497 > > The wiki doesn't mention the DELETEALIAS action. I won't have time > right now to update the wiki. > > Thanks, > Shawn > >
