This may be an infrastructure issue because according to Parabuild everything
is fine:
http://parabuild.viewtier.com:8080/parabuild/build/log.htm?logid=3405&buildrunid=2568
Slava
- Original Message -
From:
To:
Sent: Thursday, March 29, 2007 4:23 PM
Subject: Lucene nightly build failu
FYI: Patch submitted in http://issues.apache.org/jira/browse/LUCENE-847.
Cheers,
Ning
"Here is a patch for concurrent merge as discussed in:
http://www.gossamer-threads.com/lists/lucene/java-dev/45651?search_string=concurrent%20merge;#45651
"I put it under this issue because it helps design and
It will be great to support early termination for top-K queries within
the DAAT query processing model in Lucene. There is quite some work
published in related areas.
http://portal.acm.org/citation.cfm?id=956944 is one of them.
Am I getting it right? If a query requires top-K results, isn't it
su
javacc-uptodate-check:
javacc-notice:
[echo]
[echo] One or more of the JavaCC .jj files is newer than its
corresponding
[echo] .java file. Run the "javacc" target to regenerate the
artifacts.
[echo]
init:
clover.setup:
[mkdir] Created dir: /tmp/lucen
