Uses of Class
org.pentaho.di.trans.cluster.TransSplitter

Packages that use TransSplitter

org.pentaho.di.trans

This package contains the classes needed to define and execute transformations.

Uses of TransSplitter in org.pentaho.di.trans

Methods in org.pentaho.di.trans that return TransSplitter

static TransSplitter

Trans.executeClustered(TransMeta transMeta, TransExecutionConfiguration executionConfiguration) Execute the transformation in a clustered fashion.

Methods in org.pentaho.di.trans with parameters of type TransSplitter

static int	Trans.cleanupCluster(LogChannelInterface log, TransSplitter transSplitter) Cleanup the cluster, including the master and all slaves, and return the number of errors that occurred.
static void	Trans.cleanupSlaveServer(TransSplitter transSplitter, SlaveServer slaveServer, TransMeta slaveTransMeta) Cleanup the slave server as part of a clustered transformation.
static void	Trans.executeClustered(TransSplitter transSplitter, TransExecutionConfiguration executionConfiguration) Executes an existing TransSplitter, with the transformation already split.
static Result	Trans.getClusteredTransformationResult(LogChannelInterface log, TransSplitter transSplitter, Job parentJob) Gets the clustered transformation result.
static long	Trans.monitorClusteredTransformation(LogChannelInterface log, TransSplitter transSplitter, Job parentJob) Monitors a clustered transformation every second, after all the transformations in a cluster schema are running. Now we should verify that they are all running as they should. If a transformation has an error, we should kill them all. This should happen in a separate thread to prevent blocking of the UI. When the master and slave transformations have all finished, we should also run a cleanup on those transformations to release sockets, etc.
static long	Trans.monitorClusteredTransformation(LogChannelInterface log, TransSplitter transSplitter, Job parentJob, int sleepTimeSeconds) Monitors a clustered transformation every second, after all the transformations in a cluster schema are running. Now we should verify that they are all running as they should. If a transformation has an error, we should kill them all. This should happen in a separate thread to prevent blocking of the UI. When the master and slave transformations have all finished, we should also run a cleanup on those transformations to release sockets, etc.