Re: Atomic Update and stored copy-fields

2013-05-06 Thread raulgrande83
We have defined those copyfield destinations as stored because we have experienced some problems when highlighting in them. These fields have different Tokenizers and Analyzers. We have found that if we search in one of them but highlight in a different one some words that doesn't match the first q

Re: Atomic Update and stored copy-fields

2013-04-29 Thread Erick Erickson
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 exami