These issues all depend so much on each other, i would suggest to simply try Lucene-2.9-dev trunk (e.g. from downloaded from Hudson). We have this running here without any problems. The problem with unreleased Lucene is more, that if you try new features, there may be non-compatible changes until the release, so you must keep track on changes on the components you try out. In general: If everything works for you, and you have backups of your indexes, you can simply try out. If it works correctly, just use it! Patching the relased version may make it more unstable than using the development tree, that is more tested by all our committers :)
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: George Aroush [mailto:geo...@aroush.net] > Sent: Thursday, April 16, 2009 5:05 PM > To: java-dev@lucene.apache.org > Subject: RE: Lucene 2.9 status (to port to Lucene.Net) > > Thanks Mike. > > A quick follow up question. What's the status of > http://issues.apache.org/jira/browse/LUCENE-1313? Can this work be > applied > to Lucene 2.4.1 and still get it's benefit or are there other dependency / > issues with it that prevents us from doing so? > > If anyone else knows, I welcome your input. > > -- George > > > -----Original Message----- > > From: Michael McCandless [mailto:luc...@mikemccandless.com] > > Sent: Thursday, April 16, 2009 8:36 AM > > To: java-dev@lucene.apache.org > > Subject: Re: Lucene 2.9 status (to port to Lucene.Net) > > > > Hi George, > > > > There's been a sudden burst of activity lately on 2.9 development... > > > > I know there are some biggish remaining features we may want > > to get into 2.9: > > > > * The new field cache (LUCENE-831; still being iterated/mulled), > > > > * Possible major rework of Field / Document & index-time vs > > search-time Document > > > > * Applying filters via random-access API when possible & performant > > (LUCENE-1536) > > > > * Possible further optimizations to how collection works > > (LUCENE-1593) > > > > * Maybe breaking core + contrib into a more uniform set of modules > > (and figuring out how Trie(Numeric)RangeQuery/Filter fits in here) > > -- the Modularization uber-thread. > > > > * Further improvements to near-realtime search (using RAMDir for > > small recently flushed segments) > > > > * Many other small things and probably some big ones that I'm > > forgetting now :) > > > > So things are still in flux, and I'm really not sure on a > > release date at this point. Late last year, I was hoping for > > early this year, but it's no longer early this year ;) > > > > Mike > > > > On Wed, Apr 15, 2009 at 9:17 PM, George Aroush > > <geo...@aroush.net> wrote: > > > Hi Folks, > > > > > > This is George Aroush, I'm one of the committers on Lucene.Net - a > > > port of Java Lucene to C# Lucene. > > > > > > I'm looking at the current trunk code of yet to be released > > Lucene 2.9 > > > and I would like to port it to Lucene.Net. If I do this > > now, we get > > > the benefit of keeping our code base and release dates much > > closer to Java Lucene. > > > However, this comes with a cost of carrying over unfinished work, > > > known defects, and I have to keep an eye on new code that get > > > committed into Java Lucene which must be ported over in a > > timely fashion. > > > > > > To help me determine when is a good time to start the port > > -- keep in > > > mind, I will be taking the latest code off SVN -- I like to > > hear from > > > the Java Lucene committers (and users who are playing or > > using Lucene > > > 2.9 off SVN) about those questions: > > > > > > 1) how stable the current code in the trunk is, > > > 2) do you still have feature work to deliver or just bug fixes, and > > > 3) what's your target date to release Java Lucene 2.9 > > > > > > #1 is important, such that is anyone using it in production? > > > > > > Yes, I did look at the current open issues in JIRA, but > > that doesn't > > > help me answer the above questions. > > > > > > Regards, > > > > > > -- George > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > > > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
