Hi Alex, The copyField fix (SOLR-4567) will be part of 4.2.1 - I backported it to the 4.2.1 branch.
By the way, did you see the workaround I posted in the SOLR-4567 description?: ----- UPDATE: Workaround: instead of using a single copyField directive matching multiple explicit source fields […] 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" /> ----- Steve On Mar 19, 2013, at 12:48 PM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > I am still trying to figure out Solr release cadence. They seem to be > pretty frequent :-) > > However, 4.2 broke one of my config (copyField one) and I am now curious > when the release that fixes it will be out. I know it is fixed in the > source already. > > Regards, > Alex. > P.s. I also have a suggested DIH minor feature (with big consequences :-) ) > that I believe is all ready to be incorporated (including tests), but not > sure how to convince anybody to look at it (SOLR-4530). > > Personal blog: http://blog.outerthoughts.com/ > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > - Time is the quality of nature that keeps events from happening all at > once. Lately, it doesn't seem to be working. (Anonymous - via GTD book)