use of org.apache.derby.iapi.services.cache.CacheFactory in project derby by apache.
the class RAMAccessManager method conglomCacheInit.
/**
************************************************************************
* Conglomerate Cache routines:
**************************************************************************
*/
/**
* ACCESSMANAGER CONGLOMERATE CACHE -
* <p>
* Every conglomerate in the system is described by an object which
* implements Conglomerate. This object basically contains the parameters
* which describe the metadata about the conglomerate that store needs
* to know - like types of columns, number of keys, number of columns, ...
* <p>
* It is up to each conglomerate to maintain it's own description, and
* it's factory must be able to read this info from disk and return it
* from the ConglomerateFactory.readConglomerate() interface.
* <p>
* This cache simply maintains an in memory copy of these conglomerate
* objects, key'd by conglomerate id. By caching, this avoids the cost
* of reading the conglomerate info from disk on each subsequent query
* which accesses the conglomerate.
* <p>
* The interfaces and internal routines which deal with this cache are:
* conglomCacheInit() - initializes the cache at boot time.
*/
/**
* Initialize the conglomerate cache.
* <p>
* Simply calls the cache manager to create the cache with some hard
* coded defaults for size.
* <p>
* @exception StandardException Standard exception policy.
*/
private void conglomCacheInit() throws StandardException {
// Get a cache factory to create the conglomerate cache.
CacheFactory cf = (CacheFactory) startSystemModule(org.apache.derby.shared.common.reference.Module.CacheFactory);
// Now create the conglomerate cache.
conglom_cache = cf.newCacheManager(this, AccessFactoryGlobals.CFG_CONGLOMDIR_CACHE, 200, 300);
}
Aggregations