I took a swag at applying SOLR-1873 to branch_3x. It applied mostly, most
of the rest of the issues where Zookeeper integrations, and those
appliedly cleanly by hand.
There were also a few constants and such that need to be pulled in from trunk.
At the moment, it passes all the tests. I have not actually used it yet,
and probably won't for a few weeks, but if someone else wants to try it out:
http://github.com/collectiveintellect/lucene-solr/tree/branch_3x-cloud
Have at it.
enjoy,
-jeremy
On Thu, Oct 28, 2010 at 11:21:12PM +0200, Jan H?ydahl / Cominvent wrote:
> Hi,
>
> I would aim for reindexing on branch3_x, which will be the 3.1 release soon.
> I don't know if SOLR-1873 applies cleanly to 3_x now, but it would surely be
> less effort to have it apply to 3_x than to 1.4. Perhaps you can help
> backport the patch to 3_x?
>
> --
> Jan H?ydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> On 28. okt. 2010, at 03.04, Jeremy Hinegardner wrote:
>
> > Hi all,
> >
> > I see that as of r1022188 Solr Cloud has been committed to trunk.
> >
> > I was wondering about the stability of Solr Cloud on trunk. We are
> > planning to do a major reindexing soon (within 30 days), several billion
> > docs,
> > and would like to switch to a Solr Cloud based infrastructure.
> >
> > We are wondering should use trunk as it is now that SOLR-1873 is applied, or
> > should we take SOLR-1873 and apply it to Solr 1.4.1.
> >
> > Has anyone used 1.4.1 + SOLR-1873? In production?
> >
> > Thanks,
> >
> > -jeremy
> >
> > --
> > ========================================================================
> > Jeremy Hinegardner jer...@hinegardner.org
> >
>
--
========================================================================
Jeremy Hinegardner jer...@hinegardner.org
