Super! Thanks for testing this & posting...
Mike
<[EMAIL PROTECTED]> wrote:
I don't think creating an IndexWriter is very expensive at all.
Ah ok. I tested it. Creating an IndexWriter on an index with 10.000
docs
(about 15 MB) takes about 200 ms.
This is a very cheap operation for me ;
> I don't think creating an IndexWriter is very expensive at all.
Ah ok. I tested it. Creating an IndexWriter on an index with 10.000 docs
(about 15 MB) takes about 200 ms.
This is a very cheap operation for me ;)
I only saw the many calls in init() which reads files and so on and
therefore I to
I don't think creating an IndexWriter is very expensive at all.
Especially compared to creating an IndexReader, for example.
Mike
<[EMAIL PROTECTED]> wrote:
For what time is the 2.4 release planned?
Not really sure at this point ...
Hm. Digging into IndexWriter#init it seems that this is
> > For what time is the 2.4 release planned?
>
> Not really sure at this point ...
Hm. Digging into IndexWriter#init it seems that this is a really expensive
operation and thus my self made "commit" too. Isn't it?
-
To unsubsc
<[EMAIL PROTECTED]> wrote:
For what time is the 2.4 release planned?
Not really sure at this point ...
Mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> In 2.4, commit() sets the rollback point. So abort() will
> roll index
> back to the last time you called commit() (or to when the writer was
> opened if you haven't called commit).
>
> In 2.3, your only choice is to close & re-open the writer to reset
> the rollback point.
OK, thank yo
<[EMAIL PROTECTED]> wrote:
Then, you can call close() to commit the changes to the index, or
abort() to rollback the index to the starting state (when the writer
was opened).
As I understand the docs, the index will get rolled back to the
state as it
was when the index was opened.
How can
> Then, you can call close() to commit the changes to the index, or
> abort() to rollback the index to the starting state (when the writer
> was opened).
As I understand the docs, the index will get rolled back to the state as it
was when the index was opened.
How can I achieve a rollback which o
d a new
> > commit() method can be used to periodically commit without closing if
> > you want to.
> >
> > Mike
> >
> > Sergey Kabashnyuk <[EMAIL PROTECTED]> wrote:
> >> Hi.
> >> I have a question about transactions in Lucene.
> >
<[EMAIL PROTECTED]> wrote:
Hi.
I have a question about transactions in Lucene.
Lets say I have 1000 Documents and want to add all of them or none of
them(if something happen) to the index.
What the best strategy to do it in multithreaded environment?
Sergey Kaba
Hi.
> I have a question about transactions in Lucene.
>
> Lets say I have 1000 Documents and want to add all of them or none of
> them(if something happen) to the index.
>
> What the best strategy to do it in multithreaded environm
Hi.
I have a question about transactions in Lucene.
Lets say I have 1000 Documents and want to add all of them or none of
them(if something happen) to the index.
What the best strategy to do it in multithreaded environment?
Sergey Kabashnyuk
12 matches
Mail list logo
