lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: Fields with Field.Store.NO and Field.Index.ANALYZED not being indexed
Date Tue, 31 Aug 2010 01:22:18 GMT
"if you do not have access to the original contents" is the key if Uwe's
comment. You do not need a separate field at all, it all depends upon
your situation. There's no problem in indexing AND storing f field.

HTH
Erick

On Sun, Aug 29, 2010 at 11:33 PM, Constantine Vetoshev
<gepardcv@gmail.com>wrote:

> "Uwe Schindler" <uwe@thetaphi.de> writes:
> > You cannot retrieve non-stored fields. They are analyzed and tokenized
> > during indexing and this is a one-way transformation. If you update
> > documents you have to reindex the contents. If you do not have access to
> the
> > original contents anymore, you may consider adding a stored-only "raw
> > document" field, that contains everything to rebuild the indexed fields.
> In
> > our installation, we have a stored field containing the JSON/XML source
> > document to do this.
>
> Thanks, that helps.
>
> Since it seems that I have to keep the raw data around, is there any
> reason not to just make that data's field both stored and analyzed? I'm
> just wondering why you use a separate stored-only field: a Lucene
> limitation or some app-specific reason?
>
> --
> Regards,
> Constantine Vetoshev
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

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