lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grant Ingersoll <>
Subject Re: Lucene 2.1, soon
Date Tue, 06 Feb 2007 02:11:46 GMT
I have a solution for the protection level (see my last comment on  
adding an Interface), but not for the ThreadLocal issue in LazyField  
construction (see the bug).  I think I may just stick with the  
original patch, unless someone has an insight.  I guess I could pass  
in the ThreadLocal and the cloneableFieldsStream, but that just feels  
ugly and ripe for error, especially since the moving the LazyField  
class into the FieldSelectorResult requires it be a private static  

On the other hand, I think it would be useful to eliminate the if/ 
else checks and allow for extending the types of FieldSelectorResults  
w/o having to modify FieldsReader

Any opinion?  If I/we don't come up w/ something by Wednesday, I will  
commit the original patch so that we can go ahead with the release.   
I could submit a "broken" patch that show what I have if that helps.


On Feb 5, 2007, at 6:59 PM, Steven Parkes wrote:

> I've been looking at 762. It does look a bit hairy, dealing with  
> all the
> protection levels of the classes. Did you come up with an approach you
> were happy with?
> -----Original Message-----
> From: Grant Ingersoll []
> Sent: Thursday, February 01, 2007 3:57 AM
> To:
> Subject: Re: Lucene 2.1, soon
> -1
> I would like a few more days  to get
> browse/LUCENE-762, as it may involve moving some classes and I don't
> want to do that after an official release.  It is not a major issue,
> but I do think it is important to get right before the release.
> Sorry for the delay.
> Thanks,
> Grant
> On Feb 1, 2007, at 6:02 AM, Michael McCandless wrote:
>> Michael Busch wrote:
>>> Michael McCandless wrote:
>>>> I plan on committing this one today.  Once that's in I think we can
>>>> and should get the release process going (Yonik had graciously
>>>> volunteered to be the release manager)?
>>> +1 for starting the release process. Especially the big new
>>> features "lazy field loading", "lockless commits" and "delete in
>>> IndexWriter" should make it a valuable upgrade for a lot of users.
>>> Additionally, there have been various patches that improve
>>> performance or prevent index corruption.
>> OK I just committed LUCENE-565 so I think we can get 2.1 started now?
>> Mike
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> --------------------------
> Grant Ingersoll
> Center for Natural Language Processing
> Read the Lucene Java FAQ at
> LuceneFAQ
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Grant Ingersoll

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message