You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Chad Small <Ch...@definityhealth.com> on 2004/03/26 20:47:12 UTC
Lucene 1.4 - lobby for final release
thanks Erik. Ok this is my official lobby effort for the release of 1.4 to final status. Anyone else need/want a 1.4 release?
Does anyone have any information on 1.4 release plans?
thanks,
chad.
-----Original Message-----
From: Erik Hatcher [mailto:erik@ehatchersolutions.com]
Sent: Fri 3/26/2004 1:25 PM
To: Lucene Users List
Cc:
Subject: Re: too many files open error
On Mar 26, 2004, at 1:33 PM, Chad Small wrote:
> Is this :) serious?
This is open-source. I'm only as serious as it would take for someone
to push it through. I don't know what the timeline is, although lots
of new features are available.
> Because we have a need/interest in the new field sorting capabilities
> and QueryParser keyword handling of dashes ("-") that would be in 1.4,
> I believe. It's so much easier to explain that we'll use a "final"
> release of Lucene instead of a "dev build" Lucene.
Why explain it?! Just show great results and let that be the
explanation :)
>
> If so, what would an expected release date be?
*shrug* - feel free to lobby for it. I don't know what else is planned
before a release.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: Lucene 1.4 - lobby for final release
Posted by "Kevin A. Burton" <bu...@newsmonster.org>.
Chad Small wrote:
>thanks Erik. Ok this is my official lobby effort for the release of 1.4 to final status. Anyone else need/want a 1.4 release?
>
>Does anyone have any information on 1.4 release plans?
>
>
Just an FYI... I've noticed a fatal bug that was introduced in 1.3rc2 ->
final. I've had to use 1.3rc2 in our application. The problem is that
during an index merge Lucene will get stuck in an infinte loop and never
terminate.
I haven't had much time to debug it but I just reverted back and we were
fine.
I'll yield to whatever decision you guys make as I don't have a patch or
a better diagnosis of the problem.
Thanks!
--
Please reply using PGP.
http://peerfear.org/pubkey.asc
NewsMonster - http://www.newsmonster.org/
Kevin A. Burton, Location - San Francisco, CA, Cell - 415.595.9965
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
IRC - freenode.net #infoanarchy | #p2p-hackers | #newsmonster
Re: Lucene 1.4 - lobby for final release
Posted by Doug Cutting <cu...@apache.org>.
Chad Small wrote:
> thanks Erik. Ok this is my official lobby effort for the release of 1.4 to final status. Anyone else need/want a 1.4 release?
>
> Does anyone have any information on 1.4 release plans?
I'd like to make an RC once I manage to fix bug #27799, which will
hopefully be soon.
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Wiki and news
Posted by Stephane James Vaucher <va...@cirano.qc.ca>.
On the wiki, I've looked up some reference for lucene community releases
to put under News (http://wiki.apache.org/jakarta-lucene/LatestNews), if
I've missed some, you can modify the page yourself (it's a wiki after
all).
sv
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: Documentation and presentations
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Mar 26, 2004, at 8:16 PM, Stephane James Vaucher wrote:
> Erik, maybe Otis and yourself should slow down on development. You
> wouldn't want your book to discuss lucene-1.3 if you release a version
> 1.5
> before it hits the stores... unless that's your master plan;)
It will cover the new Lucene 1.4 features. If Lucene 1.5 holds even
cooler features, well, we'll just have to put out an update when that
happens :)
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: Documentation and presentations
Posted by Stephane James Vaucher <va...@cirano.qc.ca>.
Erik, maybe Otis and yourself should slow down on development. You
wouldn't want your book to discuss lucene-1.3 if you release a version 1.5
before it hits the stores... unless that's your master plan;)
sv
On Fri, 26 Mar 2004, Erik Hatcher wrote:
> So far so good, Stephane, on the wiki changes - looks good!
>
> As for our book - at this point, early summer seems like when it'll
> actually be on the shelves. By the end of April we should have mostly
> everything complete, reviewed, and entirely in the publishers hands.
> *ugh* - this process takes much longer than even exaggerated estimates.
>
> Erik
>
>
> On Mar 26, 2004, at 6:00 PM, Stephane James Vaucher wrote:
>
> > Hello lucene community,
> >
> > I'll be presenting lucene at the GUJM (Java Users Group of Montreal),
> > mid-April, could you send me references, articles, presentations not
> > readily available on the lucene site (at
> > http://jakarta.apache.org/lucene/docs/resources.html)?
> >
> > Otis or Erik, I'll mention that you have written a book on lucene. When
> > will it be out?
> >
> > I'll also see if I can rearrange the wiki using the information you
> > send
> > me, and I'll contribute my presentation (in french).
> >
> > cheers,
> > sv
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: Documentation and presentations
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
So far so good, Stephane, on the wiki changes - looks good!
As for our book - at this point, early summer seems like when it'll
actually be on the shelves. By the end of April we should have mostly
everything complete, reviewed, and entirely in the publishers hands.
*ugh* - this process takes much longer than even exaggerated estimates.
Erik
On Mar 26, 2004, at 6:00 PM, Stephane James Vaucher wrote:
> Hello lucene community,
>
> I'll be presenting lucene at the GUJM (Java Users Group of Montreal),
> mid-April, could you send me references, articles, presentations not
> readily available on the lucene site (at
> http://jakarta.apache.org/lucene/docs/resources.html)?
>
> Otis or Erik, I'll mention that you have written a book on lucene. When
> will it be out?
>
> I'll also see if I can rearrange the wiki using the information you
> send
> me, and I'll contribute my presentation (in french).
>
> cheers,
> sv
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Documentation and presentations
Posted by Stephane James Vaucher <va...@cirano.qc.ca>.
Hello lucene community,
I'll be presenting lucene at the GUJM (Java Users Group of Montreal),
mid-April, could you send me references, articles, presentations not
readily available on the lucene site (at
http://jakarta.apache.org/lucene/docs/resources.html)?
Otis or Erik, I'll mention that you have written a book on lucene. When
will it be out?
I'll also see if I can rearrange the wiki using the information you send
me, and I'll contribute my presentation (in french).
cheers,
sv
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: Lucene 1.4 - lobby for final release
Posted by Stephane James Vaucher <va...@cirano.qc.ca>.
I hope nobody minds, I've added a link on the wiki to the head of
CHANGES.txt. I'm not sure if anyone is "maintaining the wiki", if not, I
can take a look at it. I could maybe rearrange things to look like
<sample-site>:
http://wiki.apache.org/avalon
</sample-site>
Any comments? I'll probably just go ahead and do it and await critisism ;)
cheers,
sv
On Fri, 26 Mar 2004, Erik Hatcher wrote:
> On Mar 26, 2004, at 3:32 PM, Stephane James Vaucher wrote:
> > I'm personally a fan of a release small but often approach, but what
> > are
> > the new features available in 1.4 (a list would be nice, on the wiki
> > perhaps)? Will there be interim builds available to try these new
> > features
> > out soon?
>
> There is a CHANGES.txt in the root of the jakarta-lucene CVS repository
> that stays pretty much current and accurate. I'm pasting it below for
> the 1.3 -> CVS HEAD changes.
>
> >
> > There seem to be no nightly builds on:
> >
> > http://cvs.apache.org/builds/jakarta-lucene/nightly/
> >
>
> I guess at this time you will have to build it yourself from CVS.
> There is one show-stopper before we can release an RC1. We must fully
> convert to ASL 2.0 (meaning every single source file needs the license
> header as well as any other files that can be tagged with it). I know
> Otis has changed some files, but we need a full sweep. There have been
> some utilities posted in a committers area to facilitate this change
> more automatically if we want to use them.
>
> Erik
>
> excerpt from CHANGES.txt
>
> 1.4 RC1
>
> 1. Changed the format of the .tis file, so that:
>
> - it has a format version number, which makes it easier to
> back-compatibly change file formats in the future.
>
> - the term count is now stored as a long. This was the one aspect
> of the Lucene's file formats which limited index size.
>
> - a few internal index parameters are now stored in the index, so
> that they can (in theory) now be changed from index to index,
> although there is not yet an API to do so.
>
> These changes are back compatible. The new code can read old
> indexes. But old code will not be able read new indexes. (cutting)
>
> 2. Added an optimized implementation of TermDocs.skipTo(). A skip
> table is now stored for each term in the .frq file. This only
> adds a percent or two to overall index size, but can substantially
> speedup many searches. (cutting)
>
> 3. Restructured the Scorer API and all Scorer implementations to take
> advantage of an optimized TermDocs.skipTo() implementation. In
> particular, PhraseQuerys and conjunctive BooleanQuerys are
> faster when one clause has substantially fewer matches than the
> others. (A conjunctive BooleanQuery is a BooleanQuery where all
> clauses are required.) (cutting)
>
> 4. Added new class ParallelMultiSearcher. Combined with
> RemoteSearchable this makes it easy to implement distributed
> search systems. (Jean-Francois Halleux via cutting)
>
> 5. Added support for hit sorting. Results may now be sorted by any
> indexed field. For details see the javadoc for
> Searcher#search(Query, Sort). (Tim Jones via Cutting)
>
> 6. Changed FSDirectory to auto-create a full directory tree that it
> needs by using mkdirs() instead of mkdir(). (Mladen Turk via Otis)
>
> 7. Added a new span-based query API. This implements, among other
> things, nested phrases. See javadocs for details. (Doug Cutting)
>
> 8. Added new method Query.getSimilarity(Searcher), and changed
> scorers to use it. This permits one to subclass a Query class so
> that it can specify it's own Similarity implementation, perhaps
> one that delegates through that of the Searcher. (Julien Nioche
> via Cutting)
>
> 9. Added MultiReader, an IndexReader that combines multiple other
> IndexReaders. (Cutting)
>
> 10. Added support for term vectors. See Field#isTermVectorStored().
> (Grant Ingersoll, Cutting & Dmitry)
>
> 11. Fixed the old bug with escaping of special characters in query
> strings: http://issues.apache.org/bugzilla/show_bug.cgi?id=24665
> (Jean-Francois Halleux via Otis)
>
> 12. Added support for overriding default values for the following,
> using system properties:
> - default commit lock timeout
> - default maxFieldLength
> - default maxMergeDocs
> - default mergeFactor
> - default minMergeDocs
> - default write lock timeout
> (Otis)
>
> 13. Changed QueryParser.jj to allow '-' and '+' within tokens:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=27491
> (Morus Walter via Otis)
>
> 14. Changed so that the compound index format is used by default.
> This makes indexing a bit slower, but vastly reduces the chances
> of file handle problems. (Cutting)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: Lucene 1.4 - lobby for final release
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Mar 26, 2004, at 3:32 PM, Stephane James Vaucher wrote:
> I'm personally a fan of a release small but often approach, but what
> are
> the new features available in 1.4 (a list would be nice, on the wiki
> perhaps)? Will there be interim builds available to try these new
> features
> out soon?
There is a CHANGES.txt in the root of the jakarta-lucene CVS repository
that stays pretty much current and accurate. I'm pasting it below for
the 1.3 -> CVS HEAD changes.
>
> There seem to be no nightly builds on:
>
> http://cvs.apache.org/builds/jakarta-lucene/nightly/
>
I guess at this time you will have to build it yourself from CVS.
There is one show-stopper before we can release an RC1. We must fully
convert to ASL 2.0 (meaning every single source file needs the license
header as well as any other files that can be tagged with it). I know
Otis has changed some files, but we need a full sweep. There have been
some utilities posted in a committers area to facilitate this change
more automatically if we want to use them.
Erik
excerpt from CHANGES.txt
1.4 RC1
1. Changed the format of the .tis file, so that:
- it has a format version number, which makes it easier to
back-compatibly change file formats in the future.
- the term count is now stored as a long. This was the one aspect
of the Lucene's file formats which limited index size.
- a few internal index parameters are now stored in the index, so
that they can (in theory) now be changed from index to index,
although there is not yet an API to do so.
These changes are back compatible. The new code can read old
indexes. But old code will not be able read new indexes. (cutting)
2. Added an optimized implementation of TermDocs.skipTo(). A skip
table is now stored for each term in the .frq file. This only
adds a percent or two to overall index size, but can substantially
speedup many searches. (cutting)
3. Restructured the Scorer API and all Scorer implementations to take
advantage of an optimized TermDocs.skipTo() implementation. In
particular, PhraseQuerys and conjunctive BooleanQuerys are
faster when one clause has substantially fewer matches than the
others. (A conjunctive BooleanQuery is a BooleanQuery where all
clauses are required.) (cutting)
4. Added new class ParallelMultiSearcher. Combined with
RemoteSearchable this makes it easy to implement distributed
search systems. (Jean-Francois Halleux via cutting)
5. Added support for hit sorting. Results may now be sorted by any
indexed field. For details see the javadoc for
Searcher#search(Query, Sort). (Tim Jones via Cutting)
6. Changed FSDirectory to auto-create a full directory tree that it
needs by using mkdirs() instead of mkdir(). (Mladen Turk via Otis)
7. Added a new span-based query API. This implements, among other
things, nested phrases. See javadocs for details. (Doug Cutting)
8. Added new method Query.getSimilarity(Searcher), and changed
scorers to use it. This permits one to subclass a Query class so
that it can specify it's own Similarity implementation, perhaps
one that delegates through that of the Searcher. (Julien Nioche
via Cutting)
9. Added MultiReader, an IndexReader that combines multiple other
IndexReaders. (Cutting)
10. Added support for term vectors. See Field#isTermVectorStored().
(Grant Ingersoll, Cutting & Dmitry)
11. Fixed the old bug with escaping of special characters in query
strings: http://issues.apache.org/bugzilla/show_bug.cgi?id=24665
(Jean-Francois Halleux via Otis)
12. Added support for overriding default values for the following,
using system properties:
- default commit lock timeout
- default maxFieldLength
- default maxMergeDocs
- default mergeFactor
- default minMergeDocs
- default write lock timeout
(Otis)
13. Changed QueryParser.jj to allow '-' and '+' within tokens:
http://issues.apache.org/bugzilla/show_bug.cgi?id=27491
(Morus Walter via Otis)
14. Changed so that the compound index format is used by default.
This makes indexing a bit slower, but vastly reduces the chances
of file handle problems. (Cutting)
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org
Re: Lucene 1.4 - lobby for final release
Posted by Stephane James Vaucher <va...@cirano.qc.ca>.
I'm personally a fan of a release small but often approach, but what are
the new features available in 1.4 (a list would be nice, on the wiki
perhaps)? Will there be interim builds available to try these new features
out soon?
There seem to be no nightly builds on:
http://cvs.apache.org/builds/jakarta-lucene/nightly/
cheers,
sv
On Fri, 26 Mar 2004, Chad Small wrote:
> thanks Erik. Ok this is my official lobby effort for the release of 1.4 to final status. Anyone else need/want a 1.4 release?
>
> Does anyone have any information on 1.4 release plans?
>
> thanks,
> chad.
>
> -----Original Message-----
> From: Erik Hatcher [mailto:erik@ehatchersolutions.com]
> Sent: Fri 3/26/2004 1:25 PM
> To: Lucene Users List
> Cc:
> Subject: Re: too many files open error
>
>
>
> On Mar 26, 2004, at 1:33 PM, Chad Small wrote:
> > Is this :) serious?
>
> This is open-source. I'm only as serious as it would take for someone
> to push it through. I don't know what the timeline is, although lots
> of new features are available.
>
> > Because we have a need/interest in the new field sorting capabilities
> > and QueryParser keyword handling of dashes ("-") that would be in 1.4,
> > I believe. It's so much easier to explain that we'll use a "final"
> > release of Lucene instead of a "dev build" Lucene.
>
> Why explain it?! Just show great results and let that be the
> explanation :)
>
> >
> > If so, what would an expected release date be?
>
> *shrug* - feel free to lobby for it. I don't know what else is planned
> before a release.
>
> Erik
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org