[
http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12429248 ]
Doron Cohen commented on LUCENE-388:
Paul, would you like to re-open this issue for (re)solving it with one of the
two recent patches (2 or 2b) - I think that
[
http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12429262 ]
Yonik Seeley commented on LUCENE-388:
-
No need to re-open Doron, I committed doron_2_IndexWriter.patch at the same
time as my first reply (shortly after you po
On 8/18/06, Michael McCandless <[EMAIL PROTECTED]> wrote:
> One would also have to worry about partially deleted segments on
> Windows... while removing a segment, some of the files might fail to
> delete (due to still being open) and some might succeed.
Yes, I think this case is handled correct
Yonik Seeley wrote:
On 8/18/06, Michael McCandless <[EMAIL PROTECTED]> wrote:
> One would also have to worry about partially deleted segments on
> Windows... while removing a segment, some of the files might fail to
> delete (due to still being open) and some might succeed.
Yes, I think this ca
On 8/20/06, Michael McCandless <[EMAIL PROTECTED]> wrote:
On deletable: yes, I'm currently GC'ing unused segments by doing a
full directory listing.
Actually, you could get a full directory listing once per IndexWriter
and keep the results up-to-date in memory (including deletes that
fail). No
Yonik Seeley wrote:
On 8/20/06, Michael McCandless <[EMAIL PROTECTED]> wrote:
On deletable: yes, I'm currently GC'ing unused segments by doing a
full directory listing.
Actually, you could get a full directory listing once per IndexWriter
and keep the results up-to-date in memory (including de
[
http://issues.apache.org/jira/browse/LUCENE-573?page=comments#action_12429287 ]
Hoss Man commented on LUCENE-573:
-
> You assume that the queryparser unescapes the quotes inside
> the phrase, but the queryparser does not unescape *any*
> escape
[
http://issues.apache.org/jira/browse/LUCENE-573?page=comments#action_12429297 ]
Yonik Seeley commented on LUCENE-573:
-
> it seems like query parser should be unescaping it automatically for you
That's my take. \" should return the user "
[ http://issues.apache.org/jira/browse/LUCENE-650?page=all ]
Hoss Man resolved LUCENE-650.
-
Resolution: Fixed
Assignee: Hoss Man
Attached patch: demonstrates bug with test, provides fix, applies cleanly,
breaks no other existing tests.
Applied and co
[ http://issues.apache.org/jira/browse/LUCENE-660?page=all ]
Yonik Seeley closed LUCENE-660.
---
Resolution: Fixed
Committed. Nice HTML output :-)
> GData html render preview
> -
>
> Key: LUCENE-660
>
I don't think you can do this. If two different writers are opened
for the same indexed, you always need to read the directory since the
other may have created new segments.
On Aug 20, 2006, at 1:35 PM, Michael McCandless wrote:
Yonik Seeley wrote:
On 8/20/06, Michael McCandless <[EMAIL PR
Hi,
In my project,I want to update the lucene's index when there has database
insertion operations,in this way,my users could search the fresh information
immediately if someone inserted the information into database.That's what I
need,could someone give me suggestions to implement my need?Than
robert engels wrote:
I don't think you can do this. If two different writers are opened for
the same indexed, you always need to read the directory since the other
may have created new segments.
This case should be OK. You have to close one IndexWriter before
opening the other (only 1 writer
13 matches
Mail list logo
