ok, let me try with some dummy documents...
On 6/16/06, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
Hi Dedian,
Can you write a self-contained test case that reproduces the problem?
Thanks,
Grant
Dedian Guo (JIRA) wrote:
> index optimize problem
> --
>
: 2.0.0
Reporter: Dedian Guo
since it is recommended to use IndexWriter and IndexSearcher once, I am not
sure if we need a function such as boolean IsOpen() to check the open status of
Writer and Searcher.
--
This message is automatically generated by JIRA.
-
If you think it was sent
index optimize problem
--
Key: LUCENE-603
URL: http://issues.apache.org/jira/browse/LUCENE-603
Project: Lucene - Java
Type: Bug
Components: Index
Versions: 1.9
Environment: CentOS 4.0 , Lucene 1.9, Eclipse 3.1
Reporter: Dedian
I am not sure if it is a question, could anybody tell me if the query syntax
can do the select...from..where job as in traditional database? I have
checked Lucene query syntax, but seems a little bit not too complex as
SQL...correct me if wrong, or there is no such requirement for searching
engine
The simplese way is to create indexsearcher instance for each searching
request
or create indexsearcher for each index folder (such as indexX, indexY,...),
then write a function to choose correct indexsearcher for related searching
request...
On 4/12/06, wenjie zheng <[EMAIL PROTECTED]> wrote
sorry for getting in wrong mail list, anyway, I get useful information from
you guys, thanks.
On 4/4/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
>
> There is a FAQ thta covers it, I just updated it since it was somewhat out
> of date and lacked some of the newest (bestest?) info about dealing
I used following code to do my range searching:
IndexSearcher searcher = new IndexSearcher("index");
String qstr = "id:[1 TO 2]";
Analyzer analyzer = new StandardAnalyzer();
QueryParser qp = new QueryParser("title",analyzer);
Query query = qp.parse(qstr);
