Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <bddd3c950704040556jc63a0a1ufe196d6922afcb7a@mail.gmail.com>
References: <bddd3c950704040556jc63a0a1ufe196d6922afcb7a@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8240F65E-5924-4161-BFC4-1B357A2D534A@apache.org>
Content-Transfer-Encoding: 7bit
From: Grant Ingersoll <gsingers@apache.org>
Subject: Re: Field.lazy setter method?
Date: Wed, 4 Apr 2007 09:07:45 -0400
To: java-user@lucene.apache.org

Lazy loading is handled through the FieldSelector interface on  
IndexReader.doc() and some variations.  There is nothing special that  
need be done during indexing to mark a field as lazy.  The isLazy  
method merely lets you know later, after loading a Document, if the  
field is, indeed, lazy.  One caveat, lazy fields become undefined if  
the underlying IndexReader is closed before accessing the field.   
Once a lazy field is loaded, however, this is no longer an issue, as  
the field value stays in memory.

-Grant

On Apr 4, 2007, at 8:56 AM, jafarim wrote:

> Hi
> I wonder why there is not setter method for the "lazy" member  
> variable in
> Field class. Does that mean the propoerty is nominal and setting it  
> does not
> have any effect, or am I missing some point?
> Any way, is there any way to tell lucene that a field is to be lazy- 
> loaded,
> from the very beginning of field construction?
>
> --jaf

--------------------------
Grant Ingersoll
Center for Natural Language Processing
http://www.cnlp.org

Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/ 
LuceneFAQ


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