Hi Chris, Even better - you can contribute with documentation - you can create jira with patch.
Thanks, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > On 22 Oct 2018, at 15:43, Chris Wareham <chris.ware...@graduate-jobs.com> > wrote: > > Hi Emir, > > Many thanks for the confirmation. I'd kind of inferred this was correct > from the paragraph starting with "Copying is done at the stream source > level", but it would be good to mention it in the "Copying Fields" > section of the Solr documentation. Should I create a JIRA issue asking > for this? > > Regards, > > Chris > > On 22/10/2018 14:28, Emir Arnautović wrote: >> Hi Chris, >> Yes you can do that. There is also type=“ignored” that you can use in such >> scenario. >> HTH, >> Emir >> -- >> Monitoring - Log Management - Alerting - Anomaly Detection >> Solr & Elasticsearch Consulting Support Training - http://sematext.com/ >>> On 22 Oct 2018, at 15:22, Chris Wareham <chris.ware...@graduate-jobs.com> >>> wrote: >>> >>> Hi folks, >>> >>> I have a number of fields defined in my managed-schema file that are used >>> as the sources for a copy field: >>> >>> <field name="body" type="text_general" indexed="false" >>> stored="true"/> >>> <field name="sectors" type="string" indexed="false" >>> stored="true" multiValued="true"/> >>> <field name="locations" type="string" indexed="false" >>> stored="true" multiValued="true"/> >>> >>> <field name="content" type="text_general" indexed="true" >>> stored="false" multiValued="true"/> >>> >>> <copyField source="body" dest="content"/> >>> <copyField source="sectors" dest="content"/> >>> <copyField source="locations" dest="content"/> >>> >>> Can I set both the indexed and stored values to false for the body, sectors >>> and locations fields since I don't want to search or retrieve them? >>> >>> Regards, >>> >>> Chris
