Hi Jay, You could use one field for both unless there is a specific requirement you are looking for that is not being met by that one field (e.g. faceting, etc). Typically, if you have a field that is marked as both "indexed" and "stored", the value that is passed while indexing to that field is stored as is. However, it's indexed based on the field type that you've specified for that field.
e.g. a description field with the field type of "text_en" would be indexed per the pipeline in the text_en fieldtype and the text as is will be stored (which is what is returned in your response in the results). Thanks, -- *Sameer Maggon* Measured Search | Solr-as-a-Service | Solr Monitoring | Search Analytics www.measuredsearch.com <https://mailtrack.io/trace/link/dca98638f8114f38d1ff30ed04feb547877c848e?url=http%3A%2F%2Fmeasuredsearch.com%2F&signature=797ba5008ecc48b8> On Sun, Jan 31, 2016 at 5:56 PM, Jay Potharaju <jspothar...@gmail.com> wrote: > Hi, > I am trying to decide if I should use text_en or string as my field type. > The fields have to be both indexed and stored for display. One solution is > to duplicate fields, one for indexing other for display.One of the field > happens to be a description field which I would like to avoid duplicating. > Solr should return results when someone searches for John or john.Is > storing a copy of the field the best way to go about this problem? > > > Thanks >
