RE: Custom filters & document numbers

2005-02-24 Thread Vanlerberghe, Luc
An IndexReader will always see the same set of documents. Even if another process deletes some documents, adds new ones or optimizes the complete index, your IndexReader instance will not see those changes. If you detect that the Lucene index changed (e.g. by calling IndexReader.getCurrentVersion(

RE: QUERYPARSER + LEXECIAL ERROR

2005-01-17 Thread Vanlerberghe, Luc
Hi, There's nothing wrong with the searchWrd string itself (I ran a few variations of it trough my test setup) The '\' characters in the source are escapes for the java compiler and will never be seen by lucene. The only way I found to produce a similar Exception (org.apache.lucene.queryParser.Pa

RE: HTMLParser.getReader returning null

2004-11-12 Thread Vanlerberghe, Luc
If you use the Field.Text(String name, Reader value) version of the Field.Text constructor, the field is tokenized and indexed but *not* stored. This means you will be able to search and find that document, but to know the original contents you will have to store a copy of it elsewhere. The Field

RE: BooleanQuery - TooManyClauses

2004-10-26 Thread Vanlerberghe, Luc
Even if you need to be able to search on ranges that include the time, you could benefit from adding a few extra fields to your documents. For example: add a year field and an hour field: If the user then specifies a range between 2001-08-10 11:00 and 2004-10-11 13:00, you break it up behind the