@Pratik: you should have investigated. I understand that solved your issue, but in case you needed norms it doesn't make sense that cause your index to grow up by a factor of 30. You must have faced a nasty bug if it was just the norms.
@Howe : *Compound File* .cfs, .cfe An optional "virtual" file consisting of all the other index files for systems that frequently run out of file handles. *Frequencies* .doc Contains the list of docs which contain each term along with frequency *Field Data* .fdt The stored fields for documents *Positions* .pos Stores position information about where a term occurs in the index *Term Index* .tip The index into the Term Dictionary So, David, you confirm that those two index have : 1) same number of documents 2) identical documents ( + 1 new field each not indexed) 3) same number of deleted documents 4) they both were born from scratch ( an empty index) The matter is still suspicious : - Cfs seems to highlight some sort of malfunctioning during indexing/committing in relation with the OS. What was the way of commiting you were using ? - .doc, .pos, .tip -> they shouldn't change, assuming both the indexes are optimised, you are adding a not indexed field, those data structures shouldn't be affected - the stored content as well, too much of an increment Can you send us the full configuration for the new field ? You don't want, norms, positions and frequencies for it. But in case they are the issue, you may have found some very edge case, because also enabling all of them you shouldn't incur in such a penalty for just an additional tiny field ----- --------------- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
