I don't believe this would work. My understanding (please correct if I have this wrong) is that the underlying Lucene document ids have a potential to change and so when a newSearcher is created the caches must be regenerated and not copied.
Matt -----Original Message----- From: YouPeng Yang [mailto:yypvsxf19870...@gmail.com] Sent: Thursday, July 24, 2014 10:26 AM To: solr-user@lucene.apache.org Subject: To warm the whole cache of Solr other than the only autowarmcount Hi I think it is wonderful to have caches autowarmed when commit or soft commit happens. However ,If I want to warm the whole cache other than the only autowarmcount,the default the auto warming operation will take long long ~~long time.So it comes up with that maybe it good idea to just change the reference of the caches of the newsearcher with the caches of the oldsearcher. It will increase the time of the autowarming,also increase the query time of NRT. It is just not a mature idea.I am pust this idea,and hope to get more hints or help to make more cleat about the idea. regards
