On Tue, Feb 18, 2025 at 05:44:23PM +0000, Rahul Goswami wrote: > 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.
Yes, it should have. I had read it. > 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 Thank you. This is good to know. In https://solr.apache.org/guide/solr/latest/indexing-guide/copy-fields.html there is no list of defined attributes and no statement that copyField accepts the same attributes as field. The only attributes documented there are source, dest, and maxChars. > 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. It's not stated in the page linked above whether the field value is copied or referenced, and I've found no way to infer it. > From this point on, the copy field gets stored(if stored=true), analyzed > and indexed (if indexed=true) just like any other field. Again, good to know. Thank you. This answers my immediate concern: yes, we should pay attention to the attributes of the source field and the copyField so that we can avoid un-necessary duplication of storage. We're working with full texts of academic papers, which can be quite large, and we might save quite a bit of storage and I/O with careful schema design. > 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 > > -- 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
signature.asc
Description: PGP signature
