[
http://issues.apache.org/jira/browse/LUCENE-554?page=comments#action_12412749 ]
Patrick Kimber commented on LUCENE-554:
---
Otis, Sorry my comment was addressed to Nadav (who posted the issue).
He says in the description of the issue, "I will post here
Is there a chance that LUCENE-485 makes it into 2.0? There's a patch
attached and Doug added a +1 in the comments...
It reduces the time IndexWriter keeps the commit lock while cleaning up
obsolete files/segments.
The commit lock should be held while the 'working set' is changing, but
is not nece
Marvin Humphrey wrote:
On May 20, 2006, at 12:01 AM, Robert Engels wrote:
Maybe don't cache the term pages, then, just cache the frequently
requested
terms themselves.
That sounds like a winner. Search term frequencies follow a power law
distribution. Cache the top 20% or so in an LRU
Chris Hostetter wrote:
I believe Doug's suggestion was to hold off just long enough to fix any
egregious bugs, or apply any "safe" patches for bugs that have allready
been fixed but not yet applied.
Yes, that's my intent. I've been hoping that a consensus about which
bugs are urgent will appe
I propose to make Lucene release 2.0.0 this Friday, the 26th of May.
If there are bugs whose patches that you feel should be included in this
release, please lobby to have them committed prior to this date.
Doug
-
To unsubscr
On Montag 22 Mai 2006 18:42, Doug Cutting wrote:
> I propose to make Lucene release 2.0.0 this Friday, the 26th of May.
+1
--
http://www.danielnaber.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mai
+1 as well.
On May 22, 2006, at 2:16 PM, Daniel Naber wrote:
On Montag 22 Mai 2006 18:42, Doug Cutting wrote:
I propose to make Lucene release 2.0.0 this Friday, the 26th of May.
+1
--
http://www.danielnaber.de
-
To unsu
: In case Explanation is also to explain what a Filter does, it would need to
: have both a match flag and a score value.
that's a good point, i hadn't considered hte possibility of "explaining"
filters much ... but there's no reason why the "valueO 'f an explanation
couldn't be an optional part
On Mon, 2006-05-22 at 09:42 -0700, Doug Cutting wrote:
> I propose to make Lucene release 2.0.0 this Friday, the 26th of May.
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Mon, 2006-05-22 at 09:42 -0700, Doug Cutting wrote:
I propose to make Lucene release 2.0.0 this Friday, the 26th of May.
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Seems Doug is correct. I ran our tests through the profiler. Most of the
time is spent in reading/parsing SegmentTermDocs (see the very interesting
attached profiler output).
I was amazed at how much time is spent in both readVint and readByte().
Seems high, but I think it is mainly due to the num
Robert Engels wrote:
I was amazed at how much time is spent in both readVint and readByte().
Seems high, but I think it is mainly due to the number of invocations.
Profilers have been known to exaggerate this sort of thing. These are
central routines of Lucene, but they're also pretty simple
+1
Doug Cutting wrote:
I propose to make Lucene release 2.0.0 this Friday, the 26th of May.
If there are bugs whose patches that you feel should be included in
this release, please lobby to have them committed prior to this date.
Doug
+1
If you want, I can try doing this, but I'm likely going to have some questions.
I think the first one would be:
Is http://wiki.apache.org/jakarta-lucene/ReleaseTodo up to date?
Otis
- Original Message
From: Doug Cutting <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Monda
The WorkspaceInfo class in unneccessary. The WorkspaceDetails can be
persisted directly if reworked.
-Original Message-
From: Doug Cutting [mailto:[EMAIL PROTECTED]
Sent: Monday, May 22, 2006 5:48 PM
To: java-dev@lucene.apache.org
Subject: Re: caching term information?
Robert Engels wrot
+1
Send instant messages to your online friends http://uk.messenger.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
17 matches
Mail list logo
