com.bigdata.resources
Class AbstractPrepareTask<T>
java.lang.Object
com.bigdata.journal.AbstractTask<T>
com.bigdata.resources.AbstractResourceManagerTask<T>
com.bigdata.resources.AbstractPrepareTask<T>
- All Implemented Interfaces:
- ITask<T>, Callable<T>
- Direct Known Subclasses:
- CompactingMergeTask, IncrementalBuildTask, JoinIndexPartitionTask, MoveTask, ScatterSplitTask, SplitIndexPartitionTask, SplitTailTask
public abstract class AbstractPrepareTask<T>
- extends AbstractResourceManagerTask<T>
Base class for the prepare phase which reads on the old journal.
- Version:
- $Id: AbstractPrepareTask.java 2265 2009-10-26 12:51:06Z thompsonbry $
- Author:
- Bryan Thompson
| Fields inherited from class com.bigdata.journal.AbstractTask |
checkpointNanoTime, concurrencyManager, isReadWriteTx, nanoTime_assignedWorker, nanoTime_beginWork, nanoTime_finishedWork, nanoTime_submitTask, readOnly, taskCounters, timestamp, transactionManager, tx |
|
Method Summary |
protected abstract void |
clearRefs()
Method is responsible for clearing the SoftReferences held by
ViewMetadata for the source view(s) on the old journal. |
| Methods inherited from class com.bigdata.journal.AbstractTask |
assertResource, assertRunning, assertUnisolated, call, clearLoggingContext, doTask, dropIndex, getCommitTime, getIndex, getJournal, getOnlyResource, getResource, getResourceManager, getTaskCounters, getTaskName, getTimestamp, isResource, registerIndex, setupLoggingContext, toString |
AbstractPrepareTask
public AbstractPrepareTask(ResourceManager resourceManager,
long timestamp,
String resource)
- Parameters:
resourceManager - timestamp - resource -
AbstractPrepareTask
public AbstractPrepareTask(ResourceManager resourceManager,
long timestamp,
String[] resource)
- Parameters:
resourceManager - timestamp - resource -
clearRefs
protected abstract void clearRefs()
- Method is responsible for clearing the
SoftReferences held by
ViewMetadata for the source view(s) on the old journal.
Note: This method MUST be invoked in order to permit those references to
be cleared more eagerly than the end of the entire asynchronous overflow
operation (which is when the task references would themselves go out of
scope and become available for GC).
Copyright © 2006-2009 SYSTAP, LLC. All Rights Reserved.