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 requires that is).
I think the best solution (assuming it works) is to try to lock a version of Lucene 4.0 while upgrading Solr. I'll have to test to see if this works or not, but at least it's something. On Wed, Dec 7, 2011 at 9:02 AM, Mike Sokolov <soko...@ifactory.com> wrote: > 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 need to stick w/3.x for now. You might be in a > different situation if you really need the 4.0 changes. Maybe you can just > stick w/the current trunk and take responsibility for patching critical > bugfixes, hoping you won't have to recreate your index too many times... > > -Mike > > > On 12/06/2011 09:48 PM, Jamie Johnson wrote: >> >> 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<dar...@ontrenet.com> wrote: >> >>> >>> 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 (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. I'm not looking for anything hard, just trying >>>> to plan as much as possible understanding that this is one of the >>>> implications of using trunk. >>>> >>>> On Tue, Dec 6, 2011 at 6:48 PM, Robert Muir<rcm...@gmail.com> wrote: >>>> >>>>> >>>>> On Tue, Dec 6, 2011 at 6:41 PM, Jamie Johnson<jej2...@gmail.com> >>>>> 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-unsubscr...@lucene.apache.org >>>>> For additional commands, e-mail: java-user-h...@lucene.apache.org >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org >>>> For additional commands, e-mail: java-user-h...@lucene.apache.org >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: java-user-h...@lucene.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-user-h...@lucene.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
