[SOLR-4567] copyField source glob matching explicit field(s) stopped working in Solr 4.2

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2
• Fix Version/s: 4.2.1, 4.3, 6.0
• Component/s: Schema and Analysis
• Assignee: Steven Rowe
• Reporter: Steven Rowe
• Created: 13/Mar/13 04:40
• Updated: 09/May/16 18:46
• Resolved: 13/Mar/13 08:28

Description

Alexandre Rafalovitch reported on the solr-user mailing list http://markmail.org/message/sqhzxaet55wztldq that a copyField directive that worked under Solr 4.1 has stopped working under Solr 4.2:

<field name="addr_from" type="email" indexed="true" stored="true" required="true" />
<field name="addr_to" type="email" multiValued="true" indexed="true" stored="true" required="true" />
<copyField source="addr_*" dest="text" />

I'm 99% sure that matching multiple explicit fields is not the problem, but rather the issue is that I committed changes under SOLR-4503 to handle additional previously unhandled changes, but I didn't consider this case, and so introduced the regression. The table on SOLR-3798 that attempted to describe all possible combinations of copyField directives does not include this case.

UPDATE: Workaround: instead of using a single copyField directive matching multiple explicit source fields, like the above example, use multiple copyField directives, each giving an explicit field name. So the above example using this workaround would be:

<field name="addr_from" type="email" indexed="true" stored="true" required="true" />
<field name="addr_to" type="email" multiValued="true" indexed="true" stored="true" required="true" />
<copyField source="addr_from" dest="text" />
<copyField source="addr_to" dest="text" />

Issue Links

• is related to: SOLR-4650 copyField doesn't work with source globs that don't match dynamic fields