If i'm understanding this suggestion correctly, the main change in
observable behavior will be that actions performed by a "reader" will
never block or invalidate actions performed by a "writer" -- writers on
the other hand can still block eachother.
This seems like it might be the opposite of wh
I would like to discuss an additional approach, that requires small changes
to current Lucene implementation. Here, the index version (currently in
segments file) is maintained in a separate file, and is used to synchronize
between readers and writers, without requiring readers to create/obtain any
Hi Grant,
Does it mean you already have maven script for Nutch, Lucene or Hadoop
(or all of them)?
I would be interested in it. Could you send me it or post somewhere no
the web or create wiki page for it?
Regards,
Lukas
On 8/23/06, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
Hey Dejan,
Don't
See below
On Aug 24, 2006, at 4:17 PM, Michael McCandless (JIRA) wrote:
[ http://issues.apache.org/jira/browse/LUCENE-664?
page=comments#action_12430293 ]
Michael McCandless commented on LUCENE-664:
---
OK I did some more small fixes to the section
[
http://issues.apache.org/jira/browse/LUCENE-565?page=comments#action_12430361 ]
Jason Rutherglen commented on LUCENE-565:
-
This IndexWriter seems to work. Thanks. Great work!
> Supporting deleteDocuments in IndexWriter (Code and Perf
[ http://issues.apache.org/jira/browse/LUCENE-664?page=all ]
Michael McCandless updated LUCENE-664:
--
Attachment: scoring-small-fixes2.patch
> [PATCH] small fixes to the new scoring.html doc
> ---
>
>
[
http://issues.apache.org/jira/browse/LUCENE-664?page=comments#action_12430293 ]
Michael McCandless commented on LUCENE-664:
---
OK I did some more small fixes to the sections "Query Classes" and "Changing
Similarity". Just added some m
i think everyone like "one-click installer"
2006/8/23, Dejan Nenov <[EMAIL PROTECTED]>:
Hi Grant,
We tried Maven, but found it extremely tedious - yes I admit we are
influenced by the commercial nature of our work and have to tradeoff our
purist software engineering tendencies with pragmatic d
