| Package | Description |
|---|---|
| io.druid.query.lookup | |
| io.druid.query.lookup.namespace | |
| io.druid.server.lookup.namespace | |
| io.druid.server.lookup.namespace.cache |
| Class and Description |
|---|
| CacheScheduler
Usage:
|
| NamespaceExtractionCacheManager
Usage:
|
| Class and Description |
|---|
| CacheScheduler
Usage:
|
| CacheScheduler.EntryImpl
This class effectively contains the whole state and most of the logic of
CacheScheduler.Entry, need to be a separate class
because the Entry must not be referenced from the runnable executed in CacheScheduler.cacheManager's ExecutorService,
that would be a leak preventing the Entry to be collected by GC, and therefore CacheScheduler.EntryImpl.entryCleaner to be run by
the JVM. |
| CacheScheduler.VersionedCache |
| Class and Description |
|---|
| CacheScheduler
Usage:
|
| CacheScheduler.EntryImpl
This class effectively contains the whole state and most of the logic of
CacheScheduler.Entry, need to be a separate class
because the Entry must not be referenced from the runnable executed in CacheScheduler.cacheManager's ExecutorService,
that would be a leak preventing the Entry to be collected by GC, and therefore CacheScheduler.EntryImpl.entryCleaner to be run by
the JVM. |
| CacheScheduler.VersionedCache |
| Class and Description |
|---|
| CacheHandler |
| CacheScheduler.CacheState |
| CacheScheduler.Entry |
| CacheScheduler.EntryImpl
This class effectively contains the whole state and most of the logic of
CacheScheduler.Entry, need to be a separate class
because the Entry must not be referenced from the runnable executed in CacheScheduler.cacheManager's ExecutorService,
that would be a leak preventing the Entry to be collected by GC, and therefore CacheScheduler.EntryImpl.entryCleaner to be run by
the JVM. |
| CacheScheduler.NoCache |
| CacheScheduler.VersionedCache |
| NamespaceExtractionCacheManager
Usage:
|
Copyright © 2011–2017. All rights reserved.