StandardAnalyzer(), create);
Document document = new Document();
document.add(new Field(data, string, Store.YES, Index.TOKENIZED));
iw.addDocument(document);
iw.close();
}
}
//-end -TestMultiReaderIsCurrent.java --
--
regards,
Volodymyr Bychkoviak
[
http://issues.apache.org/jira/browse/LUCENE-415?page=comments#action_12417314 ]
Volodymyr Bychkoviak commented on LUCENE-415:
-
Yonik,
is this right code?
if (file.length() == 0) {
// This can happen if there was a previous crash
[
http://issues.apache.org/jira/browse/LUCENE-415?page=comments#action_12417315 ]
Volodymyr Bychkoviak commented on LUCENE-415:
-
moreover
FSDirectory.createDirectory() which calls FSIndexOutput constructor already has
a check for file
[
http://issues.apache.org/jira/browse/LUCENE-521?page=comments#action_12370737 ]
Volodymyr Bychkoviak commented on LUCENE-521:
-
You are not closing indexWriter. IndexWriter should be closed to flush cached
documents...
Documents do not get
[
http://issues.apache.org/jira/browse/LUCENE-521?page=comments#action_12370740 ]
Volodymyr Bychkoviak commented on LUCENE-521:
-
you are not closing ramWriter. It also should be closed. 10 is default value of
maxBufferedDocs. i.e. number
we should not only delete segment but remove it from index structure
(i.e. SegmentInfos).
Volodymyr Bychkoviak wrote:
followup:
in SegmentReader.doCommit()
we can add check
if (deletedDocs.count()==deletedDocs.size()) {
//delete this segment
}
deleting segment can be done by code
SegmentReader use this code?
Does it all make sense?
Volodymyr Bychkoviak wrote:
if index is updated continuously then in some moment we will have one
or more segments in index that have all documents deleted.
As long as deleting happens in IndexReader can we delete such 'empty'
segments
functionality
Patch attached here to discuss it first
(should I post it directly to jira?)
--
regards,
Volodymyr Bychkoviak
Index:
D:/programming/projects/componence/lucene-dev/src/java/org/apache/lucene/index/IndexWriter.java
[
http://issues.apache.org/jira/browse/LUCENE-476?page=comments#action_12359321 ]
Volodymyr Bychkoviak commented on LUCENE-476:
-
sorry for unfinished description
add public method getClausesCount() to BooleanQuery that returns number
[ http://issues.apache.org/jira/browse/LUCENE-476?page=all ]
Volodymyr Bychkoviak updated LUCENE-476:
Attachment: BooleanQuery.diff
BooleanQuery add public method that returns number of clauses this query
Type: Improvement
Components: Search
Reporter: Volodymyr Bychkoviak
Attachments: BooleanQuery.diff
BooleanQuery add public method getClausesCount() that returns number of clauses
this query.
current ways of getting clauses count are:
1).
int clausesCount = booleanQuery.getClauses
Type: Improvement
Components: Store
Reporter: Volodymyr Bychkoviak
recently I found that RAMDirectory(Directory dir, boolean closeDir)
constructor uses memory inefficiently.
files from source index are read entirely intro memory as single byte array
which is after all is thrown away
[
http://issues.apache.org/jira/browse/LUCENE-475?page=comments#action_12359036 ]
Volodymyr Bychkoviak commented on LUCENE-475:
-
Oh, I didn't described my solution...
Solution is simle: use 1k buffer to copy files from source index to ram files
be remove for now.
Luc
-Original Message-
From: Volodymyr Bychkoviak [mailto:[EMAIL PROTECTED]
Sent: donderdag 17 november 2005 11:46
To: java-dev@lucene.apache.org
Subject: Re: missing class in svn
I found problem.
Iterable is part of 1.5 jdk
but AFAIK lucene is compatible with 1.4
appropriate value inside application but if
I want to test same query in Luke I get TooManyClausesException.
--
regards,
Volodymyr Bychkoviak
15 matches
Mail list logo
