Daniel Naber wrote:
On Monday 15 November 2004 09:50, Christiaan Fluit wrote:
Is it correct that Lucene 1.4.2 already had the desired behaviour? It's
parse method looks like this (MFQP revision 1.4):
That version doesn't work as expected for queries where all the terms are
required,
Is it correct that Lucene 1.4.2 already had the desired behaviour? It's
parse method looks like this (MFQP revision 1.4):
public static Query parse(String query, String[] fields, Analyzer
analyzer)
throws ParseException
{
BooleanQuery bQuery = new BooleanQuery();
for (in
Christoph Goller wrote:
1) Keep an IndexReader/Searcher open on your index in order to guarantee
reed access and a consistent index during the whole process.
2) Open a new IndexReader and delete all the documents that you want to
update.
3) Close the IndexReader (makes the deletions visible for any
Giulio Cesare Solaroli wrote:
is there any architectural reason while an IndexWriter could not
delete a document?
[snip]
In this situation, I try to keep the same IndexWriter open as much as
possible, in order to avoid any unnecessary fragmentation of the
index.
Before indexing any document, I can
