lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Lu <>
Subject Re: Switching from Store.YES to Store.NO
Date Wed, 06 Jan 2010 06:28:07 GMT
Just curious, will it be adjusted during indexing when merging segments?


Chris Lu
Instant Scalable Full-Text Search On Any Database/Application
Lucene Database Search in 3 minutes:
DBSight customer, a shopping comparison site, (anonymous per request) got 2.6 Million Euro

Michael McCandless wrote:
> Making that switch is fine.
> The change will not be retroactive, ie, all previously indexed docs
> with Store.YES will continue to store their fields.  But new docs
> won't store their fields if you specify Store.NO.
> I don't think this (what happens when certain schema changes happen
> mid-indexing) is well documented, in general.
> Mike
> On Tue, Jan 5, 2010 at 12:01 PM, Babak Farhang <> wrote:
>> Hi,
>> A review of the requirements of the project I'm working on has led us
>> to conclude that going forward we don't need Lucene to store certain
>> field values--just index.  Owing to the large size of the data, we
>> can't really afford to reindex everything, (Going forward, we plan to
>> treat these fields as if they were never stored.) Which brings up my
>> question.  What effect, if any, does switching to Store.NO have when
>> existing documents in the index already use Store.YES for that field?
>> Will the change take effect for the new docs added to the index?  Are
>> there any side-effects to consider?
>> Also, more generally, since the Lucene API does not guard against
>> changing the document "schema" as the index is being built, I imagine
>> the effects of such mid-stream "schema" changes might be documented
>> somewhere.  Please share, if you know of such a document.
>> Regards,
>> -Babak
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message