You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by "Peter A. Friend" <oc...@corp.earthlink.net> on 2005/06/14 18:46:27 UTC
fields that change over time
From reading the docs, it appears that Lucene supports addition of
new fields over time to an existing index. This is very handy for
folks whose indexing requirements change over time. My question has
to do with a change in an existing field name that goes from being
unstored to stored. Obviously any previously indexed document will
not have the stored value, but will Lucene handle a mix of unstored
and stored values for a given field name, within the same index?
Thanks in advance,
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: fields that change over time
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Jun 14, 2005, at 12:46 PM, Peter A. Friend wrote:
> From reading the docs, it appears that Lucene supports addition of
> new fields over time to an existing index. This is very handy for
> folks whose indexing requirements change over time. My question has
> to do with a change in an existing field name that goes from being
> unstored to stored. Obviously any previously indexed document will
> not have the stored value, but will Lucene handle a mix of unstored
> and stored values for a given field name, within the same index?
Yes, it will handle that situation just fine. Stored fields are per-
document, so it won't matter that some documents used field "foo" as
unstored and other documents stored their value in "foo".
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org