[ http://issues.apache.org/jira/browse/LUCENE-709?page=all ]
Chuck Williams updated LUCENE-709:
--
Attachment: ramDirSizeManagement.patch
> [PATCH] Enable application-level management of IndexWriter.ramDirectory size
>
[
http://issues.apache.org/jira/browse/LUCENE-709?page=comments#action_12448923 ]
Chuck Williams commented on LUCENE-709:
---
Mea Culpa! Bad bug on my part. Thanks for spotting it!
I believe the solution is simple. RAMDirectory.files is a
[ http://issues.apache.org/jira/browse/LUCENE-669?page=all ]
Michael Busch reassigned LUCENE-669:
Assignee: Michael Busch
> finalize()-methods of FSDirectory.FSIndexInput and FSDirectory.FSIndexOutput
> try to close already closed file
> ---
[
http://issues.apache.org/jira/browse/LUCENE-669?page=comments#action_12448908 ]
Michael Busch commented on LUCENE-669:
--
The method closeFile() belongs to FSDirectory.FSIndexOutput, so I can't call it
in FSDirectory.FSIndexInput.close(). (
[
http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12448902 ]
Michael McCandless commented on LUCENE-701:
---
Oooh -- I would love to!
> Lock-less commits
> -
>
> Key: LUCENE-701
>
[ http://issues.apache.org/jira/browse/LUCENE-669?page=all ]
Otis Gospodnetic updated LUCENE-669:
Lucene Fields: [Patch Available]
Looks fine to me.
Maybe change this a bit:
public void close() throws IOException {
-if (!isClone)
- file.
[ http://issues.apache.org/jira/browse/LUCENE-701?page=all ]
Otis Gospodnetic updated LUCENE-701:
Lucene Fields: [Patch Available] (was: [New])
> Lock-less commits
> -
>
> Key: LUCENE-701
> URL: http:/
[
http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12448892 ]
Otis Gospodnetic commented on LUCENE-701:
-
Steven - I don't see any issues with this going in before 2.1. As a matter of
fact, this may be a sufficiently
[ http://issues.apache.org/jira/browse/LUCENE-651?page=all ]
Otis Gospodnetic updated LUCENE-651:
Lucene Fields: [Patch Available]
Assignee: Otis Gospodnetic
FieldCache bit us in the ass recently, so I'm looking at other FieldCache
issues.
[
http://issues.apache.org/jira/browse/LUCENE-532?page=comments#action_12448877 ]
Andrzej Bialecki commented on LUCENE-532:
--
Hadoop cannot (yet) change file position when writing. All files are
write-once, i.e. once they are closed the
[
http://issues.apache.org/jira/browse/LUCENE-669?page=comments#action_12448786 ]
Michael McCandless commented on LUCENE-669:
---
This patch looks good to me. It still applies cleanly to the current [Nov 10
2006] svn head, and I think th
[
http://issues.apache.org/jira/browse/LUCENE-532?page=comments#action_12448780 ]
Michael McCandless commented on LUCENE-532:
---
Also: I like the idea of never doing "seek" when writing. The less
functionality we rely on from the filesy
[
http://issues.apache.org/jira/browse/LUCENE-532?page=comments#action_12448774 ]
Michael McCandless commented on LUCENE-532:
---
Sorry, I meant "dup of LUCENE-704 " above.
> [PATCH] Indexing on Hadoop distributed file system
> --
[
http://issues.apache.org/jira/browse/LUCENE-532?page=comments#action_12448770 ]
Michael McCandless commented on LUCENE-532:
---
I think this is the same issue as LUCENE-532 (I just marked that one as a dup).
But there was one difference
[ http://issues.apache.org/jira/browse/LUCENE-704?page=all ]
Michael McCandless resolved LUCENE-704.
---
Resolution: Duplicate
I think this is a dup of LUCENE-532
> Lucene should have a "write once" mode
> --
>
>
[
http://issues.apache.org/jira/browse/LUCENE-709?page=comments#action_12448758 ]
Yonik Seeley commented on LUCENE-709:
-
> That code too was without the thread-safety measure Yonik suggests so I don't
> know what overhead that will add.
swi
[
http://issues.apache.org/jira/browse/LUCENE-709?page=comments#action_12448736 ]
Mark Harwood commented on LUCENE-709:
-
This is a really nice addition to have which takes some of the guess-work out
of buffer sizing based on numbers of docs.
[
http://issues.apache.org/jira/browse/LUCENE-709?page=comments#action_12448725 ]
Yonik Seeley commented on LUCENE-709:
-
Thanks Chuck, I think I like this additional view/control into IndexWriter, and
I don't think opening this up more furth
[
http://issues.apache.org/jira/browse/LUCENE-552?page=comments#action_12448712 ]
Michael McCandless commented on LUCENE-552:
---
That second exception is a bit different from the first: the second hits NPE
when calling RAMDirectory.file
[
http://issues.apache.org/jira/browse/LUCENE-554?page=comments#action_12448707 ]
Michael McCandless commented on LUCENE-554:
---
With lockless commits LUCENE-701 (which does not use file renaming at all) this
issue will be resolved.
>
[ http://issues.apache.org/jira/browse/LUCENE-425?page=all ]
Michael McCandless closed LUCENE-425.
-
Resolution: Duplicate
Assignee: (was: Lucene Developers)
I think this one is a dup of LUCENE-665
The intermittant errors on WIN32 came dow
21 matches
Mail list logo
