On 7/24/2015 3:48 PM, shamik wrote: > Here's the part which I'm not able to understand. I've for e.g. Source A, B, > C and D in index. Each source contains "n" number of documents. Now, out of > these, a bunch of documents in A and B are tagged with MediaType. I took the > following steps: > > 1. Delete all documents tagged with MediaType for A and B. Documents from C > and D are not touched. > > 2. Re-Index documents which were tagged with MediaType > > 3. Run Optimization > > Still, I keep seeing this exception. Does this mean, content from C and D > are impacted even though they are not tagged with MediaType ?
Do any docs from C and D have that field? Never mind whether you need to run your operation on them ... do they have the field? If so, then when the facet code (which knows about the schema and the fact that it has docValues) looks at those segments, they do not have *any* docValues tagging for that field. This likely would cause big explosions. This lack of docValues tagging probably survives an optimize. Even if they don't have the field, there may be something about the Lucene format that the docValues support just doesn't like when the original docs were indexed without docValues on that field. Rebuilding the *entire* index is recommended for most schema changes, especially those like docValues that affect very low-level code implementations. Solr hides lots of low-level Lucene details from the administrator, but makes use of those details to do its job. Making sure your config and schema match what was present when the index was built is sometimes critical. Thanks, Shawn
