Decoupling IndexReader would for 3.0 would be great. This includes making public SegmentReader, MultiSegmentReader.
A constructor like new SegmentReader(TermsDictionary termDictionary, TermPostings termPostings, ColumnStrideFields csd, DocIdBitSet deletedDocs); Where each class is abstract and can be implemented in an optional way. Decouple rollback, commit, IndexDeletionPolicy from DirectoryIndexReader into a class like SegmentsVersionSystem which could act as the controller for reopen types of methods. There could be a SegmentVersionSystem that manages the versioning of a single segment. I'd rather figure out these things before worrying too much about generics which although nice for being able to read the code, doesn't matter if the code changes dramatically and is deprecated. > of the alternative "big bang" approach. Is this the type of thing you mean by the "big bang" approach? On Fri, Dec 12, 2008 at 4:44 AM, Grant Ingersoll <gsing...@apache.org>wrote: > We agreed in the vote that we would allow generics, etc. in 3.0 including > the removal of non-generic versions of the same methods. In other words, we > aren't strictly following the way we went from 1.9 to 2.0. > > I sent a thread on 2.9/3.0 planning a while ago, but got no responses... > > > On Dec 12, 2008, at 5:18 AM, Michael McCandless wrote: > > >> Taking this to java-dev (off Jira)... >> >> Mark Miller (Jira) wrote: >> >> > I thought there were some that wanted to change some of the API to java >> > 5 for the 3.0 release, cause I thought back compat was less restricted >> > 2-3. I guess mabye that won't end up happening, if it was going to, it >> > seems we'd want to deprecate what will be changed in 2.9. >> >> I could easily be confused on this... but I thought 3.0 is the first >> release that's allowed to include Java 1.5 only APIs (eg generics). >> >> Meaning, we could in theory intro APIs with generics with 3.0, >> deprecating the non-generics versions, and then 4.0 (sounds insanely >> far away!) would be the first release that could remove the deprecated >> non-generics versions? >> >> That said, I think the "plan" is to release 2.9 soonish (early next >> year?), and then fairly quickly turnaround a 3.0 that doesn't have too >> many changes except the removal of the deprecated (in 2.9) APIs. Ie >> in practice it won't be until 3.1 when we would intro new >> (generics-based) APIs. >> >> Mike >> > > -------------------------- > Grant Ingersoll > > Lucene Helpful Hints: > http://wiki.apache.org/lucene-java/BasicsOfPerformance > http://wiki.apache.org/lucene-java/LuceneFAQ > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > >
