You can also use a dynamic field as the destination. So with the configuration below, if your document had a field 'foo_ss' it would create a 'foo_facets'
< dynamicField name="*_facets" type="string" indexed="true" stored="true" required="false" multiValued="true" /> <dynamicField name="*_ss" type="text_general" indexed="true" stored="true" required="false" multiValued="true" /> <copyField source="*_ss" dest="*_facets"/> - Andy - On Thu, Feb 2, 2023 at 6:38 PM Jeremy Buckley - IQ-C <jeremy.buck...@gsa.gov.invalid> wrote: > Yes, you should be able to use a dynamicField as the source. That's really > just a shorthand to keep you from having to enumerate all possible field > names in the schema. I don't think order matters, but I tend to put > copyField directives after all the field and dynamicField definitions, for > readability if nothing else. >
