That's probably as official as anything ever gets around here.
-- Jack Krupansky
-Original Message-
From: Mark Miller
Sent: Friday, January 04, 2013 11:47 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
I'm going to
Well, i hope this won't spoil everything then:
https://issues.apache.org/jira/browse/SOLR-4260
I'll continue tests monday
-Original message-
> From:Mark Miller
> Sent: Fri 04-Jan-2013 17:54
> To: solr-user@lucene.apache.org
> Subject: Re: Solr 4 (CloudSolrServe
I'm going to push *hard* for a Jan release. Woe to those that get in my way :)
- Mark
On Jan 4, 2013, at 11:37 AM, Shawn Heisey wrote:
> On 1/4/2013 8:54 AM, Luis Cappa Banda wrote:
>> Any release stimation date, Mark? I heard something about January. I was
>> considering using 4.0 for producti
Thanks Mark.
-Original Message-
From: Mark Miller [mailto:markrmil...@gmail.com]
Sent: Friday, January 04, 2013 9:51 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
CloudSolrServer can be used for indexing and is smart about
On 1/4/2013 8:54 AM, Luis Cappa Banda wrote:
Any release stimation date, Mark? I heard something about January. I was
considering using 4.0 for production but if 4.1 release is incomming I
could wait a little more.
I'm not a committer, but I contribute the occasional patch and keep an
eye on t
Any release stimation date, Mark? I heard something about January. I was
considering using 4.0 for production but if 4.1 release is incomming I
could wait a little more.
2013/1/4 Mark Miller
> CloudSolrServer can be used for indexing and is smart about indexing since
> it knows the current clus
CloudSolrServer can be used for indexing and is smart about indexing since it
knows the current cluster state.
For 4.0 I'd use one per collection because there is a bug around this fixed in
the upcoming 4.1 (using one for more than one collection).
In fact, if you are moving to 4, it's a good i