lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nadav Har'El" <>
Subject Re: 1.9 RC1
Date Sun, 19 Feb 2006 10:50:19 GMT
Dan Armbrust <> wrote on 17/02/2006 08:50:53
> Short summary - The Constructor for IndexWriter currently will only
> create an index in a folder if you set the boolean create flag to true.
>   But then, if you want to append to that index, you have to set the
> create flag to false (otherwise it overwrites)
> In my use cases, I seldom want to overwrite an index - but I often
> create new ones, and append to existing ones.  Forgetting to switch the
> boolean flag between the initial create and the append causes data loss.


I agree: as a new user of Lucene, the first thing I wanted to do in my
was to open an existing index, or if one doesn't yet exist, create it. I
it very strange that this natural usage pattern wasn't naturally supported
Lucene. I ended up doing something complex like opening the index once with
create=false, and if that failed, try again with create=true, although this
additional problems like trying to recreate the index when we actually got
error which was not caused by a non-existant index.

So I'm not sure the solution is to change the semantics of the existing
constructor, but I think Lucene definitely need a new constructor or
function that will do "the right thing" for opening a potentially-existing

Nadav Har'El.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message