Hm, it seems that I'm screwed with CLucnee 0.9.21 because in fact I'm not
using an IndexWriter but an IndexModifier - and nowhere in the IndexModifier
documentation there's a mention of "commit":
http://clucene.sourceforge.net/doc/html/classlucene_1_1index_1_1IndexModifier.html
- Mike
aka...@gmail
Hi!
Is there a way to open an IndexWriter with autoCommit=true when using
CLucene 0.9.21 or is it a 2_3_2 branch only option?
In the documentation I saw this option:
void setCommitLockTimeout (int64_t commitLockTimeout)
* Sets the maximum time to wait for a commit lock (in milliseconds).
Hi Mike,
>
> I never saw the test suite before (shame on me). It will be VERY useful in
> the future. Thank you very much!!
>
No blame on you. You point out an important area where our
documentation is lacking.
> I have another question - maybe someone knows the answer:
>
> It seems that CLuc
Isidor,
I never saw the test suite before (shame on me). It will be VERY useful in
the future. Thank you very much!!
I have another question - maybe someone knows the answer:
It seems that CLucene is keeping stuff in memory between the open/close of
the IndexWriter object. For example, if you cr
Hi Mike,
> Would you mind giving me a very quick example about how to use the
> BooleanQuery with 2 fields?
>
Have a look at the BooleanQuery test suite [1], where plenty of 2
field BooleanQuery instances are created. In your case, you will want
to replace the BooleanClause::SHOULD parameter wi
Hi Isodor!
Thanks for the help!
Would you mind giving me a very quick example about how to use the
BooleanQuery with 2 fields?
Thank you very much,
Mike
clucene-developers@lists.sourceforge.net wrote:
DO NOT EDIT BELOW THIS LINE
--
To reply
your format isn't too
complex.
Itamar.
-Original Message-
From: Isidor Zeuner [mailto:cluc...@quidecco.de]
Sent: Monday, September 14, 2009 7:40 PM
To: clucene-developers@lists.sourceforge.net
Subject: Re: [CLucene-dev] Finding a specific document in the index
Hi Mike,
>
> All
Hi Mike,
>
> All records have a "tag" field containing the word "tag", that's why I'm
> searching for tag:tag (to find all records and then apply filters).
>
> Is there a better way to do this? Because that way, it's so slow that we
> can't consider using that system in production.
>
Searche
