Re: copyField - why source should contain * when dest contains *?

Hey Community, I think I have got the answer to my query. This statement about *copyFields *: *The copyField command can use a wildcard (*) character in the dest > parameter only if the source parameter contains one as well.

Re: copyField - why source should contain * when dest contains *?

Hey Chris, Awesome explanation. ...then solr has no idea what full field name to use as the destination > when it seees values in a field "foo" ... should it be "1_bar" ? > "aaa_bar" ? ... "z_bar" ? all three? But how does Solr get the idea what full field name to use

Re: copyField - why source should contain * when dest contains *?

: Documentation says that we can copy multiple fields using wildcard to one : or more than one fields. correct ... the limitation is in the syntax and the ambiguity that would be unresolvable if you had a wildcard in the dest but not in the source. the wildcard is essentially a variable.

Re: copyField - why source should contain * when dest contains *?

Hey Erick, Thanks for addressing. Copyfields are intended to copy exactly one field in the input into exactly > one field in the destination, not multiple ones at the same time. Documentation says that we can copy multiple fields using wildcard to one or more than one fields. Remember that

Re: copyField - why source should contain * when dest contains *?

So how would that work? Copyfields are intended to copy exactly one field in the input into exactly one field in the destination, not multiple ones at the same time. If you need to do that, define multiple copyField directives. I don’t even see how that would work. . Remember that Solr is also

copyField - why source should contain * when dest contains *?

Hi Community, I was just going through *Solr Ref Guide 8.1* from scratch and I was reading about* copyFields *. We have been working on copyFields in 6.6 since a year. I just wanted to refresh what we know and what we should before we