[ https://issues.apache.org/jira/browse/SOLR-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601885#comment-13601885 ]
Commit Tag Bot commented on SOLR-4567: -------------------------------------- [branch_4x commit] Steven Rowe http://svn.apache.org/viewvc?view=revision&revision=1456289 SOLR-4567: Beef up copyField tests, and assert schema conforms to test assumptions (merged trunk r1456288) > copyField source glob matching explicit field(s) stopped working in Solr 4.2 > ---------------------------------------------------------------------------- > > Key: SOLR-4567 > URL: https://issues.apache.org/jira/browse/SOLR-4567 > Project: Solr > Issue Type: Bug > Components: Schema and Analysis > Affects Versions: 4.2 > Reporter: Steve Rowe > Assignee: Steve Rowe > Fix For: 4.3, 5.0 > > Attachments: SOLR-4567.patch > > > 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: > {code:xml} > <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" /> > {code} > 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|https://issues.apache.org/jira/browse/SOLR-3798?focusedCommentId=13591583&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13591583] > 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: > {code:xml} > <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" /> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org