On May 2, 2008, at 03:33, Hardy Ferentschik wrote:
Hi there,
On Fri, 02 May 2008 01:53:02 +0200, Emmanuel Bernard <[EMAIL PROTECTED]
> wrote:
Hibernate Search 3.1 will arrive sooner than expected to align with
Hibernate Core 3.3
Great. Seems a lot of things are finally happening, espec
Hi there,
On Fri, 02 May 2008 01:53:02 +0200, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
Hibernate Search 3.1 will arrive sooner than expected to align with
Hibernate Core 3.3
Great. Seems a lot of things are finally happening, especially the
migration to maven on the core :) What is t
On 27/02/2008, Emmanuel Bernard <[EMAIL PROTECTED]> wrote:
>
> On Feb 27, 2008, at 08:40, Nick Vincent wrote:
>
> > Hi Emmanuel,
> >
> > On 26/02/2008, Emmanuel Bernard <[EMAIL PROTECTED]> wrote:
> >>
> >> On Feb 26, 2008, at 06:41, Nick Vincent wrote:
> >>>
> >>>
> >>> 2) Explaining re
On Feb 27, 2008, at 08:40, Nick Vincent wrote:
Hi Emmanuel,
On 26/02/2008, Emmanuel Bernard <[EMAIL PROTECTED]> wrote:
On Feb 26, 2008, at 06:41, Nick Vincent wrote:
2) Explaining results
This uses the new DOCUMENT_ID projection introduced in 3.0.1 to
explain query results (we need t
Hi Emmanuel,
On 26/02/2008, Emmanuel Bernard <[EMAIL PROTECTED]> wrote:
>
> On Feb 26, 2008, at 06:41, Nick Vincent wrote:
> >
> >
> > 2) Explaining results
> >
> > This uses the new DOCUMENT_ID projection introduced in 3.0.1 to
> > explain query results (we need this so the customer can
On Feb 26, 2008, at 06:41, Nick Vincent wrote:
2) Explaining results
This uses the new DOCUMENT_ID projection introduced in 3.0.1 to
explain query results (we need this so the customer can understand
their search results in the backoffice interface). I added an explain
method to both imple
Hi all,
I've been doing a lot of work with Hibernate Search recently and have
been pushing the lucene search side of it pretty hard. I've made
several changes to improve performance and functionality and have
created patches for these locally, but would like some feedback on my
approach:
1) Simi
- 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 li
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
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. St
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 r
11 matches
Mail list logo