The official documentation should be a good starting point for your questions : https://solr.apache.org/guide/solr/latest/indexing-guide/copy-fields.html
Reading the above documentation should help answer some of them and provide a general structure to your understanding of copyFields. Overall, copyFields are not much different from a regular field in terms of attributes that you can define (stored, indexed, docValues etc). It is a destination for one or more of your source fields in cases when you might want a catchall field, or a field with a different analysis pipeline for search than the one defined for the source field. What Solr does is before handing over the document for indexing to the lower Lucene layer, based on the copy field configuration in your defined schema, extracts fields from the document and copies them over to the copy field to form the "complete" document. >From this point on, the copy field gets stored(if stored=true), analyzed and indexed (if indexed=true) just like any other field. -Rahul On Tue, Feb 18, 2025 at 12:20 PM <mw...@iu.edu> wrote: > So *how* does copyField work? Do I wind up with two identical copies > of the data stored in the index (if stored='true')? Does the > copyField element accept a 'stored' attribute, and can it have a > different value than the source field declares? What *are* the > defined attributes for copyField, and do they interact with the source > field's attributes? Where should I have found answers to these > questions? > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > library.indianapolis.iu.edu >
