On Tue, Aug 4, 2015, at 06:40 PM, Shawn Heisey wrote: > On 8/4/2015 10:15 AM, wwang525 wrote: > > I waited until the indexing process finished successfully. > > > > I also set default value for these fields and I can see from simply query > > that the data was fine. The error happened after I execute a faceted query. > > There's not enough information here to answer the question Alexandre > needed answered -- did you reindex *everything* in the core with the > changed schema.xml file? I recommend deleting the index directory > entirely before reloading the core. > > You might wonder why this is necessary. Here's why: When you change > your schema, nothing happens to the existing data in the index. When > Solr tries to access that data, it uses the schema as a guide to > interpreting that data. If the index contains rows that have a field > built with a SortableIntField definition and then Solr tries to access > that data with a different definition (such as TrieIntField), there's a > good chance that an unrecoverable error will occur, because the formats > are very different on the disk. > > https://wiki.apache.org/solr/HowToReindex
Also, what led you to the conclusion that TrieIntFields would perform better? They are the recommended field type in Solr 4+, but I'm not aware of the performance benefits (doesn't mean there aren't!) Trie fields give significant benefit, when used with a precisionStep, for range queries, but that's not what you are talking abou there. Upayavira
