I'd ask it a different way, why in the world would you store the destinations of copyFields? It just bloats your index to no good purpose since all the sources are stored.
As you can tell, I don;t have a good answer for your question, but for an explicit warning like that, I'd heed it and/or examine the code.... Best Erick On Fri, Apr 26, 2013 at 3:24 AM, raulgrande83 <raulgrand...@hotmail.com> wrote: > Hello everybody, > > We are using last version of Solr (4.2.1) and making some tests on Atomic > Updates. > The Solr wiki says that: /(...) requires that all fields in your SchemaXml > must be configured as stored="true" except for fields which are <copyField/> > destinations -- which must be configured as stored="false" (...)/ > > We have all of our fields defined as stored, also those which are > <copyField/> destinations. During our tests we didn't notice anything > extrange in that fields, Atomic Updates are working fine. > Why <copyField/> destinations must be configured as stored=false since they > are going to be overwritten by their sources? > > Thank you! > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Atomic-Update-and-stored-copy-fields-tp4059129.html > Sent from the Solr - User mailing list archive at Nabble.com.
