You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Chris Hostetter <ho...@fucit.org> on 2008/10/01 00:38:39 UTC
Re: draft 2.4 announcement
: The next release will be 2.9. After that will be 3.0, which will
: remove all deprecated APIs from 2.9 and will be the first release of
: Lucene to require JRE 1.5. The timing on these two releases is not
: yet known.
I would move that para to the end, possibly starting with "SPECIAL NOTE:"
... while it's important to raise awareness about the upcoming game
plan, we want to lead with info about what's changed in 2.4 -- you don't
want people who are just skimming to get confused.
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: draft 2.4 announcement
Posted by Michael McCandless <lu...@mikemccandless.com>.
OK I did that. Here's the current draft:
Release 2.4.0 of Lucene is now available!
With 2.4 we have relaxed the backwards compatibility policy of the
Fieldable interface: we now allow changes on a case by case basis.
This means any custom classes that implement Fieldable will need to be
updated. This was done to accommodate the new omitTf() method (to do
pure boolean searching).
Many new features, fixes and optimizations have happened since 2.3,
including:
* New InstantiatedIndex (contrib/instantiated): RAM-based index that
enables much faster searching than RAMDirectory.
* New IndexWriter constructors now default autoCommit to false.
* New commit() method in IndexWriter lets you control when changes
are made visible & permanent in the index.
* A machine or OS crash, or power loss, while IndexWriter is writing
to an index will no longer corrupt the index.
* TimeLimitedCollector adds timeout to searches
* Delete documents by Query in IndexWriter
* Pure boolean indexing (no frequency, positions nor payloads are
indexed) using Field.setOmitTf()
* A new Directory implementation, NIOFSDirectory, using java.nio's
APIs to allow multiple threads to read from the same open file
without locking.
* IndexWriter.expungeDeletes() reclaims disk space from deleted
documents by merging away segments that have deletions.
* All filters now return a DocIdSet instead of java.util.BitSet,
making filters more efficient and flexible.
* Searching with a Filter is more efficient: now the filter is
applied to a document before scoring is done.
* IndexReader can be opened with new readOnly=true mode, which gives
better performance in a multi-threaded environment.
The detailed changes are here:
<URL to 2.4 Changes.html>
Lucene 2.4 includes index format changes that are not readable by older
versions of Lucene. Lucene 2.4 can both read and update older Lucene
indexes. Adding to an index with an older format will cause it to be
converted to the newer format.
Binary and source distributions are available at
http://www.apache.org/dyn/closer.cgi/lucene/java/
Lucene artifacts are also available in the Maven2 repository at
http://repo1.maven.org/maven2/org/apache/lucene/
NEXT RELEASE
The next release will be 2.9. After that will be 3.0, which will
remove all deprecated APIs from 2.9 and will be the first release of
Lucene to require JRE 1.5. The timing on these two releases is not
yet known.
Mike
Nadav Har'El wrote:
> On Sun, Oct 05, 2008, Michael McCandless wrote about "Re: draft 2.4
> announcement":
>>
>> I think you're right, we should mention this.
>>
>> How about changing that bullet like this?:
>>
>> * All filters now return a DocIdSet instead of java.util.BitSet,
>> making filters more efficient and flexible. Searching with a
>> Filter is now more efficient: now the filter is applied to a
>> document before scoring is done.
>
> Thanks, it's better I think.
>
> Maybe it even deserves its own bullet - I don't think there's too much
> connection between the two improvements?
>
> Thanks,
> Nadav.
>
> --
> Nadav Har'El | Sunday, Oct 5 2008, 7
> Tishri 5769
> IBM Haifa Research Lab
> |-----------------------------------------
> |Tact: The ability to describe
> others as
> http://nadav.harel.org.il |they see themselves. - Abraham
> Lincoln
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: draft 2.4 announcement
Posted by Nadav Har'El <ny...@math.technion.ac.il>.
On Sun, Oct 05, 2008, Michael McCandless wrote about "Re: draft 2.4 announcement":
>
> I think you're right, we should mention this.
>
> How about changing that bullet like this?:
>
> * All filters now return a DocIdSet instead of java.util.BitSet,
> making filters more efficient and flexible. Searching with a
> Filter is now more efficient: now the filter is applied to a
> document before scoring is done.
Thanks, it's better I think.
Maybe it even deserves its own bullet - I don't think there's too much
connection between the two improvements?
Thanks,
Nadav.
--
Nadav Har'El | Sunday, Oct 5 2008, 7 Tishri 5769
IBM Haifa Research Lab |-----------------------------------------
|Tact: The ability to describe others as
http://nadav.harel.org.il |they see themselves. - Abraham Lincoln
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: draft 2.4 announcement
Posted by Michael McCandless <lu...@mikemccandless.com>.
I think you're right, we should mention this.
How about changing that bullet like this?:
* All filters now return a DocIdSet instead of java.util.BitSet,
making filters more efficient and flexible. Searching with a
Filter is now more efficient: now the filter is applied to a
document before scoring is done.
Mike
Nadav Har'El wrote:
> On Tue, Sep 30, 2008, Michael McCandless wrote about "Re: draft 2.4
> announcement":
>> * All filters now return a DocIdSet instead of java.util.BitSet,
>> making filters more efficient and flexible.
>
> Hi Michael, I was looking at how filtering works, and I noticed
> there is,
> I believe, another very big change.
>
> Previously, if I remember correctly, when a Filter was added to a
> query,
> it worked on the HitCollector level, with each matching document being
> checked against the filter. The new code is more efficient when the
> filter
> only contains a small number of "on" documents, because now the
> scorer's
> skipTo is actually used.
>
> Isn't this a change worth mentioning, or am I just imagining things?
> (If I
> am, sorry.. Interestingly, I found in CHANGES.txt a mention of
> LUCENE-1169
> which is about fixing a bug in that new code, but I don't see any
> mention
> of that new code being written).
>
> Thanks,
>
> Nadav.
>
>
> --
> Nadav Har'El | Sunday, Oct 5 2008, 6
> Tishri 5769
> IBM Haifa Research Lab
> |-----------------------------------------
> |Anyone who quotes me in their
> sig is an
> http://nadav.harel.org.il |idiot. -- Rusty Russell's sig.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: draft 2.4 announcement
Posted by Nadav Har'El <ny...@math.technion.ac.il>.
On Tue, Sep 30, 2008, Michael McCandless wrote about "Re: draft 2.4 announcement":
> * All filters now return a DocIdSet instead of java.util.BitSet,
> making filters more efficient and flexible.
Hi Michael, I was looking at how filtering works, and I noticed there is,
I believe, another very big change.
Previously, if I remember correctly, when a Filter was added to a query,
it worked on the HitCollector level, with each matching document being
checked against the filter. The new code is more efficient when the filter
only contains a small number of "on" documents, because now the scorer's
skipTo is actually used.
Isn't this a change worth mentioning, or am I just imagining things? (If I
am, sorry.. Interestingly, I found in CHANGES.txt a mention of LUCENE-1169
which is about fixing a bug in that new code, but I don't see any mention
of that new code being written).
Thanks,
Nadav.
--
Nadav Har'El | Sunday, Oct 5 2008, 6 Tishri 5769
IBM Haifa Research Lab |-----------------------------------------
|Anyone who quotes me in their sig is an
http://nadav.harel.org.il |idiot. -- Rusty Russell's sig.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
Re: draft 2.4 announcement
Posted by Michael McCandless <lu...@mikemccandless.com>.
Good idea -- done:
Release 2.4.0 of Lucene is now available!
With 2.4 we have relaxed the backwards compatibility policy of the
Fieldable interface: we now allow changes on a case by case basis.
This means any custom classes that implement Fieldable will need to be
updated. This was done to accommodate the new omitTf() method (to do
pure boolean searching).
Many new features, fixes and optimizations have happened since 2.3,
including:
* New InstantiatedIndex (contrib/instantiated): RAM-based index that
enables much faster searching than RAMDirectory.
* New IndexWriter constructors now default autoCommit to false.
* New commit() method in IndexWriter lets you control when changes
are made visible & permanent in the index.
* A machine or OS crash, or power loss, while IndexWriter is writing
to an index will no longer corrupt the index.
* TimeLimitedCollector adds timeout to searches
* Delete documents by Query in IndexWriter
* Pure boolean indexing (no frequency, positions nor payloads are
indexed) using Field.setOmitTf()
* A new Directory implementation, NIOFSDirectory, using java.nio's
APIs to allow multiple threads to read from the same open file
without locking.
* IndexWriter.expungeDeletes() reclaims disk space from deleted
documents by merging away segments that have deletions.
* All filters now return a DocIdSet instead of java.util.BitSet,
making filters more efficient and flexible.
* IndexReader can be opened with new readOnly=true mode, which gives
better performance in a multi-threaded environment.
The detailed changes are here:
<URL to 2.4 Changes.html>
Lucene 2.4 includes index format changes that are not readable by older
versions of Lucene. Lucene 2.4 can both read and update older Lucene
indexes. Adding to an index with an older format will cause it to be
converted to the newer format.
Binary and source distributions are available at
http://www.apache.org/dyn/closer.cgi/lucene/java/
Lucene artifacts are also available in the Maven2 repository at
http://repo1.maven.org/maven2/org/apache/lucene/
NEXT RELEASE
The next release will be 2.9. After that will be 3.0, which will
remove all deprecated APIs from 2.9 and will be the first release of
Lucene to require JRE 1.5. The timing on these two releases is not
yet known.
Mike
On Sep 30, 2008, at 6:38 PM, Chris Hostetter wrote:
>
> : The next release will be 2.9. After that will be 3.0, which will
> : remove all deprecated APIs from 2.9 and will be the first release of
> : Lucene to require JRE 1.5. The timing on these two releases is not
> : yet known.
>
> I would move that para to the end, possibly starting with "SPECIAL
> NOTE:"
> ... while it's important to raise awareness about the upcoming game
> plan, we want to lead with info about what's changed in 2.4 -- you
> don't
> want people who are just skimming to get confused.
>
>
>
>
> -Hoss
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org