Class BasicETLLoadFunction

java.lang.Object

com.kingsrook.qqq.backend.core.processes.implementations.etl.basic.BasicETLLoadFunction

All Implemented Interfaces:

BackendStep

public class BasicETLLoadFunction
extends Object
implements BackendStep

Function body for performing the Load step of a basic ETL process.

Constructor Summary

Constructors

Constructor	Description
BasicETLLoadFunction()

Method Summary

Modifier and Type	Method	Description
void	run(RunBackendStepInput runBackendStepInput, RunBackendStepOutput runBackendStepOutput)	Execute the backend step - using the request as input, and the result as output.
void	setReturnStoredRecords(boolean returnStoredRecords)	Setter for returnStoredRecords
void	setTransaction(QBackendTransaction transaction)	Setter for transaction

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

BasicETLLoadFunction

public BasicETLLoadFunction()

Method Details

run

public void run(RunBackendStepInput runBackendStepInput,
 RunBackendStepOutput runBackendStepOutput)
         throws QException

Description copied from interface: BackendStep

Execute the backend step - using the request as input, and the result as output. TODO - think about - why take the Result object as a param, instead of return it? Is this way easier for inter-language operability maybe? Also - there's way too much "process-specific gunk" in the Request object - can we simplify it?

Specified by:

run in interface BackendStep

Throws:

QException

setTransaction

public void setTransaction(QBackendTransaction transaction)

Setter for transaction

setReturnStoredRecords

public void setReturnStoredRecords(boolean returnStoredRecords)

Setter for returnStoredRecords