Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of adb@teamware.com designates
 212.226.92.15 as permitted sender)
Message-ID: <465BFE56.6060601@teamware.com>
Date: Tue, 29 May 2007 13:20:06 +0300
From: Antony Bowesman <adb@teamware.com>
Organization: Teamware Group
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: Re: Does Lucene search over memory too?
References: 
 <OF4C797088.FD7B65B1-ON882572EA.0021006A-882572EA.0021A43C@il.ibm.com>
In-Reply-To: 
 <OF4C797088.FD7B65B1-ON882572EA.0021006A-882572EA.0021A43C@il.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Doron Cohen wrote:
> Antony Bowesman <adb@teamware.com> wrote on 28/05/2007 22:48:41:
> 
>> I read the new IndexWriter Javadoc and I'm unclear about this
>> autocommit.  In
>> 2.1, I thought an IndexReader opened in an IndexSearcher does not "see"
>> additions to an index made by an IndexWriter, i.e. maxDoc and
>> numDocs remain
>> constant, so the statement
>>
>> "When autoCommit is true then every flush is also a commit (IndexReader
>> instances will see each flush as changes to the index). This is
>> the default, to
>> match the behavior before 2.2"
>>
>> makes me wonder if my assumptions are wrong.  Can you clarify
>> what it means by
>> the IndexReader "seeing" changes to the index?
> 
> Antony, your assumptions were (and still are) correct - once
> an index reader is opened it is unaffected by changes to the
> underlying index. Would it be clearer if the javadoc said:
> "(An IndexReader instance will see changes to the index caused
> by flush operations that completed prior to opening that
> IndexReader instance)."?

Thanks Doron, I understood "IndexReader instance" as one that was already open, 
as it's not possible to 'open' an existing object instance, the static open() 
methods create new instances.

Your explanation clarifies things.  So, the scenario where the IndexReader sees 
changes with autocommit=true is

BEGIN
IndexWriter - open
- add documents
   - some merges/flushes occur here
   IndexReader - open
   - sees index with results of earlier merges
IndexWriter - close
END

whereas with autocommit=false, the IndexReader would see the state of the index 
at BEGIN and any merges/flushes would not show.

Perhaps the text could then be something like

"(Changes to the index caused by flush operations will be visible to an 
IndexReader when it is opened prior to closing the IndexWriter)"

It would also be worth updating the isCurrent() Javadoc to clarify its 
behaviour.  Presumably, with autocommit=false, isCurrent() will always return 
true is only using the IndexWriter to add/delete documents.

Antony


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org