Nested/child documents in Solr has been an evolutionary process, and it shows. If it were designed from the beginning, there would be first-class support for this in the schema, perhaps by having fields grouped by some notion of a document type, and then copyFields would be there as well. It's never too late for this but it's probably a big effort.
~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Sat, Oct 23, 2021 at 10:25 AM Gus Heck <[email protected]> wrote: > One option for more complex copy cases is > CloneFieldUpdateProcessorFactory, if regexes will do the trick, if not you > can probably create a custom processor that extends > FieldMutatingUpdateProcessorFactory. > > On Sat, Oct 23, 2021 at 9:44 AM Thomas Wöckinger < > [email protected]> wrote: > >> Hi! >> >> Currently it is not possible to add additional conditions on copying a >> source to a destination field. >> >> But when using Nested documents there is often the case that objects in >> different hierarchies share the same field because they have the same type >> and name. Think of a common field name like 'name' or 'description'. >> >> So to use a copy field here the only option is to create unique fields >> for each hierarchy level, which can enlarge the schema very easily. >> >> What about adding the possibility that a copy field can have rules which >> can evaluate stored fields or doc values, and only if that condition >> evaluates to true copy it to the destination field. >> >> What do you think? >> > > > -- > http://www.needhamsoftware.com (work) > http://www.the111shift.com (play) >
