While we are in constant sync due to the merge, lucene would still be
updated multiple times before a solr 4 release, and it would be subject to
happen at any time - so its really not any different.
On Wednesday, December 7, 2011, Jamie Johnson wrote:
> Yeah, biggest issue for us is we're using t
Yeah, biggest issue for us is we're using the SolrCloud features.
While I see some good things related to the Lucene and Solr code bases
being merged, this is certainly a frustrating aspect of it as I don't
require some of the changes that are in Lucene 4.0 (withstanding
anything that SolrCloud re
My personal view, as a bystander with no more information than you, is
that one has to assume there will be further index format changes before
a 4.0 release. This is based on the number of changes in the last 9
months, and the amount of activity on the dev list.
For us the implication is we
I suppose that's fair enough. Some quick googling seems that this has
been asked many times with pretty much the same response. Sorry to
add to the noise.
On Tue, Dec 6, 2011 at 9:34 PM, Darren Govoni wrote:
> I asked here[1] and it said "Ask again later."
>
> [1] http://8ball.tridelphia.net/
>
I asked here[1] and it said "Ask again later."
[1] http://8ball.tridelphia.net/
On 12/06/2011 08:46 PM, Jamie Johnson wrote:
Thanks Robert. Is there a timetable for that? I'm trying to gauge
whether it is appropriate to push for my organization to move to the
current lucene 4.0 implementation
Thanks Robert. Is there a timetable for that? I'm trying to gauge
whether it is appropriate to push for my organization to move to the
current lucene 4.0 implementation (we're using solr cloud which is
built against trunk) or if it's expected there will be changes to what
is currently on trunk.
On Tue, Dec 6, 2011 at 6:41 PM, Jamie Johnson wrote:
> Is there a timetable for when it is expected to be finalized?
it will be finalized when Lucene 4.0 is released.
--
lucidimagination.com
-
To unsubscribe, e-mail: java-user
