public interface ITask<T> extends Callable<T>
|Modifier and Type||Method and Description|
Return an appropriate view of the named index for the operation.
The journal against which the operation will be carried out.
Return the only declared resource.
Returns a copy of the array of resources declared to the constructor.
The object used to manage access to the resources from which views of the indices are created.
The object used to track events and times for the task.
If the task is running against an
ITx.UNISOLATED index, then this
will be the
IResourceManager.getLiveJournal(). If the operation
is a historical read, then it will be whatever journal is appropriate to
the historical commit point against which the task is being run.
ITx.UNISOLATED operations this exposes unconstrained
access to the journal that could be used to violate the concurrency
control mechanisms, therefore you SHOULD NOT use this unless you have a
clear idea what you are about. You should be able to write all
application level tasks in terms of
operations on the returned index.
Note: For example, if you use the returned object to access a named index
and modify the state of that named index, your changes WILL NOT be
noticed by the checkpoint protocol in
nullif no journal has data for that timestamp, including when a historical journal with data for that timestamp has been deleted.
IllegalStateException- if more than one resource was declared.
When the task is isolated by a transaction, then the index will be isolated by the transaction using the appropriate isolation level. If the transaction is read-only, then the index will not be writable.
When the task is a read-only unisolated operation, the index will be read-only and will read from the most recent committed state of the store prior to the time at which the task began to execute. If multiple index views are requested they will all use the same committed state of the store.
When the task is an unisolated write operation the index will be the unisolated writable (aka "live" or "current" index). Access to the unisolated writable indices is single-threaded. This constraint is enforced by a lock system using the named resources declared in the task constructor.
name- The index name.
NoSuchIndexException- if the named index does not exist at the time that the operation is executed.
StaleLocatorException- if the named index does not exist at the time the operation is executed and the
IResourceManagerhas information which indicates that the index partition has been split, joined or moved.
IllegalStateException- if the named index is not one of the resources declared to the constructor.
Copyright © 2006-2012 SYSTAP, LLC. All Rights Reserved.