Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of erickerickson@gmail.com
 designates 209.85.216.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=S+VCTkIdmX50KYdzj43/tcjvuQATuSXbc7e0rFsE1IonQRnEDqxEl/nBewdGbc9jId
         WKKeQ/XnPoIlW4x+CrnxJB+Ky51chcq8o8sZG6zvmrDhAlshEPjCLkGNvnBEhWPhiDiN
         O0BjEdOCj27SqOx87ZcmRw5YRDBilzUPH/6lQ=
MIME-Version: 1.0
In-Reply-To: 
 <m2mxs4zsdb.fsf@athena.local.i-did-not-set--mail-host-address--so-tickle-me>
References: 
 <m2bpecmbff.fsf@athena.local.i-did-not-set--mail-host-address--so-tickle-me>
	<359a92831003251327j110470d7r5380db0910910747@mail.gmail.com>
	<m2tymdyx1o.fsf_-_@athena.local.i-did-not-set--mail-host-address--so-tickle-me>
	<001d01cb47bb$8231cf70$86956e50$@thetaphi.de>
	<m2mxs4zsdb.fsf@athena.local.i-did-not-set--mail-host-address--so-tickle-me>
Date: Mon, 30 Aug 2010 21:22:18 -0400
Message-ID: <AANLkTim-P3qZZG5jxhJkgNnuH68+i1-xvi+XKz+HhJJB@mail.gmail.com>
Subject: Re: Fields with Field.Store.NO and Field.Index.ANALYZED not being
 indexed
From: Erick Erickson <erickerickson@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=0015175d6726816f82048f14694c

--0015175d6726816f82048f14694c
Content-Type: text/plain; charset=ISO-8859-1

"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
>
>

--0015175d6726816f82048f14694c--