You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2013/03/13 05:42:12 UTC
[jira] [Created] (SOLR-4567) copyField source glob matching
explicit field(s) stopped working in Solr 4.2
Steve Rowe created SOLR-4567:
--------------------------------
Summary: 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
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.
--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org