Apache Solr Reference Guide Covering Apache Solr 6.0

document IDs are transient, this cache is not auto-warmed. The size for the documentCache should always be
greater than max_results times the max_concurrent_queries, to ensure that Solr does not need to refetch
a document during a request. The more fields you store in your documents, the higher the memory usage of this
cache will be.
User Defined Caches
You can also define named caches for your own application code to use. You can locate and use your cache
object by name by calling the SolrIndexSearcher methods getCache() , cacheLookup() and cacheInse
rt().
If you want auto-warming of your cache, include a regenerator attribute with the fully qualified name of a class
that implements solr.search.CacheRegenerator. You can also use the NoOpRegenerator, which simply
repopulates the cache with old items. Define it with the regenerator parameter as:
regenerator="solr.NoOpRegenerator".
Query Sizing and Warming
maxBooleanClauses
This sets the maximum number of clauses allowed in a boolean query. This can affect range or prefix queries
that expand to a query with a large number of boolean terms. If this limit is exceeded, an exception is thrown.
1024
This option modifies a global property that effects all Solr cores. If multiple solrconfig.xml files
disagree on this property, the value at any point in time will be based on the last Solr core that was
initialized.
enableLazyFieldLoading
If this parameter is set to true, then fields that are not directly requested will be loaded lazily as needed. This can
boost performance if the most common queries only need a small subset of fields, especially if infrequently
accessed fields are large in size.
true
useFilterForSortedQuery
This parameter configures Solr to use a filter to satisfy a search. If the requested sort does not include "score",
Apache Solr Reference Guide 6.0
454