Why would this behavior changed from one day to the next? I ran crawl and index several times with no issues, changed the schematic xml definition of a couple of fields, ran crawl and index and produced the dataset with missing copyfields.
Sent from my iPhone > On Jan 27, 2017, at 4:07 AM, alessandro.benedetti <abenede...@apache.org> > wrote: > > I may be wrong and don't have time to check the code in details now, but I > would say you need to define the default in the destination field as well. > > The copy field should take in input the plain content of the field ( which > is null) and then pass that content to the destination field. > > Properties and attributes of the source field should not be considered at > copy field time. > So what it happens is simply you pass a null content to the destination > field. > > If you define the default in the destination field, it should work as > expected. > > N.B. it's a shot in the dark, not sure if you experienced a different > behavior previously. > > Cheers > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/How-to-alter-the-facet-query-limit-default-tp4315939p4317514.html > Sent from the Solr - User mailing list archive at Nabble.com.