I committed a fix under SOLR-4567. On Mar 13, 2013, at 12:50 AM, Steve Rowe <sar...@gmail.com> wrote:
> Yes, this is a regression, definitely my fault. Sorry Alex! > > The table on SOLR-3798 is missing this case: a glob matching one or more > explicit fields (as opposed to dynamic fields). > > I've filed a JIRA: https://issues.apache.org/jira/browse/SOLR-4567 > > On Mar 13, 2013, at 12:20 AM, "Jack Krupansky" <j...@basetechnology.com> > wrote: >> And, the wiki does not note the decommissioning of a useful feature of >> copyField. Although, the wiki is woefully incomplete when it comes to glob >> patterns for fields. > > I agree - I wrote what I thought would be a good addition to the wiki just > above the copyField combinations table on SOLR-3798. But it needs additional > verbiage to cover Alex's case. > >> Reading the table in SOLR-3798 as carefully as I can, it seems to indicate >> that your use case is supposed to be supported as case #9, leading me to >> conclude that it may simply be a bug that your use case is failing in 4.2. >> >> 9 subset pattern <field> name <copyField source="*_src_sub_i" >> dest="title"/> Yes Yes > > Alex's case is different from what I call "subset patterns" on SOLR-3798, > since that's shorthand for "subset of the language accepted by the pattern > for a referenced dynamic field". > > I'll make a copy of that table and add a case where the source value type can > be a glob matching one or more explicit fields. > > Steve > >