[hibernate-dev] Hibernate Search 3.1

[Emmanuel Bernard]

Just to let you know. Hibernate Search does not use the Lucene  
features fixed by 2.3.1. So no corruption will happen if you stay in  
a pure Hibernate Search environment. But year, moving to Lucene 2.3.1  
is probably something that should be done :)

On  Feb 25, 2008, at 07:51, Aleksander M. Stensby wrote:

> Hello!
> I think it is a very good idéa to go for Lucene 2.3.1 as soon as  
> possible, since this version fixed a corruption issue introduced in  
> 2.3.
> Se snipped text below:
>
> ---------------------------------------------------------------------- 
> -
> Release 2.3.1 of Lucene Java is now available!
>
> This release contains fixes for serious bugs in 2.3.0 that could cause
> index corruptions in autoCommit=false mode or in cases where multiple
> threads are adding documents where some have term-vector enabled
> fields and some don't.  The autoCommit option was added to IndexWriter
> with release 2.2.0. If not explicitly set to false, the IndexWriter
> runs in autoCommit=true mode.
>
> 2.3.1 does not contain any new features, API or file format changes,
> which makes it fully compatible to 2.3.0.
>
> We would like to encourage everyone who currently uses Lucene Java  
> 2.3.0
> to upgrade to 2.3.1 to prevent possible index corruptions!
>
> ---------------------------------------------------------------------- 
> --
>
> Best regards,
> Aleksander M. Stensby
>
> On Sun, 24 Feb 2008 22:10:34 +0100, Emmanuel Bernard  
> <emmanuel at hibernate.org> wrote:
>
>> I think Hibernate Search should go for 3.1 from now one in trunk:
>>   - Lucene 2.3 brings some interesting enhancements that we could  
>> benefit from.
>>   - Sanne has some interesting feedbacks on new reader strategies  
>> (warming up readers), as well as some alternative strategies to  
>> speed up mass indexing.
>>   - Hardy started working on the Null marker value and this  
>> requires some compatibility changes
>>   - John worked on adding TermVectors
>>   - Nick has been working on Similarity, which is a big feature  
>> and deserve some testing and feedbacks.
>>   - I have some additional idea to move some API to a higher level
>>
>> Do not restrain from breaking changes, but please discuss them  
>> here first before using the butchery knife :)
>>
>> If you have a todo list for Hibernate Search or if you think some  
>> Hibernate Search areas should be enhanced / reworked, feel free to  
>> discuss your ideas here.
>>
>> On a less technical note, Hibernate Search has some very good  
>> adoption both standalone and together with JBoss Seam. I had a lot  
>> of tremendous feedback at JBoss World Orlando. We even won a JBoss  
>> Innovation Awards ( well Alintec did ;) ).
>>
>> Keep up the good work!
>>
>> Emmanuel
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
>
>
> -- 
> Aleksander M. Stensby
> Senior Software Developer
> Integrasco A/S
> aleksander.stensby at integrasco.no
> Tlf.: +47 41 22 82 72
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev