solr.StrField with stored=true useless or bad?

2012-09-11 Thread sysrq
Hi, I have a StrField to store an URL. The field definition looks like this: field name=link type=string indexed=true stored=true required=true / Type string is defined as usual: fieldType name=string class=solr.StrField sortMissingLast=true / Then I realized that a StrField doesn't execute any

Re: solr.StrField with stored=true useless or bad?

2012-09-11 Thread Yonik Seeley
On Tue, Sep 11, 2012 at 7:03 PM, sy...@web.de wrote: The purpose of stored=true is to store the raw string data besides the analyzed/transformed data for displaying purposes. This is fine for an analyzed solr.TextField, but for an StrField both values are the same. So is there any reason

Re: solr.StrField with stored=true useless or bad?

2012-09-11 Thread Ahmet Arslan
The purpose of stored=true is to store the raw string data besides the analyzed/transformed data for displaying purposes. This is fine for an analyzed solr.TextField, but for an StrField both values are the same. So is there any reason to apply stored=true on a StrField as well? If you don't

Re: solr.StrField with stored=true useless or bad?

2012-09-11 Thread Amit Nithian
This is great thanks for this post! I was curious about the same thing and was wondering why fl couldn't return the indexed representation of a field if that field were only indexed but not stored. My thoughts were return something than nothing but I didn't pay attention to the fact that getting