You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Clemens Wyss DEV <cl...@mysign.ch> on 2018/01/18 07:23:01 UTC
Guideline on when a field absolutely needs to be stored?
Kind of "basic question" ... Am I right, that the only real reason to store a field (stored="true") is when I want to fetch the "originating value" from documents returned?
What about
geo-location-fields?
Any other reason/(search-)function requiring a field being stored?
Thx
Clemens
AW: Guideline on when a field absolutely needs to be stored?
Posted by Clemens Wyss DEV <cl...@mysign.ch>.
THX!
-----Ursprüngliche Nachricht-----
Von: Walter Underwood [mailto:wunder@wunderwood.org]
Gesendet: Donnerstag, 18. Januar 2018 08:27
An: solr-user@lucene.apache.org
Betreff: Re: Guideline on when a field absolutely needs to be stored?
There is a nice table for all of the field options.
https://lucene.apache.org/solr/guide/7_2/field-properties-by-use-case.html
wunder
Walter Underwood
wunder@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 17, 2018, at 11:23 PM, Clemens Wyss DEV <cl...@mysign.ch> wrote:
>
> Kind of "basic question" ... Am I right, that the only real reason to store a field (stored="true") is when I want to fetch the "originating value" from documents returned?
>
> What about
> geo-location-fields?
> Any other reason/(search-)function requiring a field being stored?
>
> Thx
> Clemens
Re: Guideline on when a field absolutely needs to be stored?
Posted by Walter Underwood <wu...@wunderwood.org>.
There is a nice table for all of the field options.
https://lucene.apache.org/solr/guide/7_2/field-properties-by-use-case.html
wunder
Walter Underwood
wunder@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 17, 2018, at 11:23 PM, Clemens Wyss DEV <cl...@mysign.ch> wrote:
>
> Kind of "basic question" ... Am I right, that the only real reason to store a field (stored="true") is when I want to fetch the "originating value" from documents returned?
>
> What about
> geo-location-fields?
> Any other reason/(search-)function requiring a field being stored?
>
> Thx
> Clemens