Re: [hibernate-dev] Hibernate Search 3.1
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 <[EMAIL PROTECTED]> 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@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Aleksander M. Stensby Senior Software Developer Integrasco A/S [EMAIL PROTECTED] Tlf.: +47 41 22 82 72 ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate Search 3.1
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 <[EMAIL PROTECTED]> 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@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Aleksander M. Stensby Senior Software Developer Integrasco A/S [EMAIL PROTECTED] Tlf.: +47 41 22 82 72 ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Maven2 upload of hibernate 3.2.6.ga
I think people mainly just "hacked it" from the previous pom. You could do that approach, or start with the stuff currently in core/ trunk although many of the dependencies have changed there. On Feb 20, 2008, at 5:41 PM, Max Bowsher wrote: Looking at MAVENUPLOAD JIRA, it looks like for Hibernate 3.2.x, upload bundles are produced by anyone who has the time and decides to do it - is that correct? If the reason why 3.2.6.ga hasn't been uploaded to central yet is because no-one's got around to it yet, I'll volunteer. Have previous bundlers left any notes, or should I just proceed based on common sense? Max. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate Search 3.1
On Sun, 24 Feb 2008 22:10:34 +0100, Emmanuel Bernard <[EMAIL PROTECTED]> wrote: I think Hibernate Search should go for 3.1 from now one in trunk: Cool. - Hardy started working on the Null marker value and this requires some compatibility changes Well, I started on it and think it is not too hard, but Emmanuel recommended to wait until 3.1. I will look into it again, but will be very busy until mit March. Another issue which I wold like to investigate further is: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-135 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 Maybe it is time to give Seam another go. The last time I tried it (about a year ago, seam-gen was not even around :( ) I found it not quite ready yet. --Hardy ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate Search 3.1
- Hardy started working on the Null marker value and this requires some compatibility changes Well, I started on it and think it is not too hard, but Emmanuel recommended to wait until 3.1. I will look into it again, but will be very busy until mit March. Another issue which I wold like to investigate further is: http:// opensource.atlassian.com/projects/hibernate/browse/HSEARCH-135 you will have to convince me that it's more useful than the problems it brings :) 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 Maybe it is time to give Seam another go. The last time I tried it (about a year ago, seam-gen was not even around :( ) I found it not quite ready yet. a year ago, seam-gen was definitively there, it must have been way before. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
