[ http://issues.apache.org/jira/browse/LUCENE-664?page=all ]
Michael McCandless updated LUCENE-664:
--
Attachment: scoring-small-fixes3.patch
Doh! You are correct. OK I re-based the diffs off the current version. Sorry
about that.
> [PATCH] small
[ http://issues.apache.org/jira/browse/LUCENE-635?page=all ]
Michael McCandless updated LUCENE-635:
--
Attachment: LUCENE-635-Aug27.patch
OK, I agree. I've updated the CHANGES.txt to state this small change.
And I've fixed SimpleFSLockFactory to mov
Transplanting this thread off of java-user to discuss a more java-dev
question I have (below):
http://www.gossamer-threads.com/lists/lucene/java-user/39382
Yonik Seeley wrote:
On 8/27/06, Doron Cohen <[EMAIL PROTECTED]> wrote:
I plan to submit an update to that patch later today accommod
I'm working on the lock-less commit patch, and came across what seems
to be a bug in the current Lucene sources:
If you have an index that has separate norms (.sN or .fN files), and
you open a reader against this index, and then try to use another
reader to change (& commit) the norms, that seco
[
http://issues.apache.org/jira/browse/LUCENE-665?page=comments#action_12430919 ]
Doron Cohen commented on LUCENE-665:
> just to confirm, is it the COMMIT lock that's throwing these
> unhandled exceptions (not the WRITE lock)?
> If so, lock
: If you have an index that has separate norms (.sN or .fN files), and
: you open a reader against this index, and then try to use another
: reader to change (& commit) the norms, that second reader will hit an
: IOException (Access Denied) on Windows during commit because the first
setNorms is d
Hi all,
I use multi-threads to do indexing work, sometimes I get invalid handle
exception. I am certain that I use the hit results before closing the
reader. What's wrong with me? Pls help me!
--
Thanks,
Jiang