Class StreamedETLBackendStep
java.lang.Object
com.kingsrook.qqq.backend.core.processes.implementations.etl.streamed.StreamedETLBackendStep
- All Implemented Interfaces:
BackendStep
- Direct Known Subclasses:
StreamedETLFilesystemBackendStep
Backend step to do a streamed ETL
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected void
postTransform
(List<QRecord> qRecords, RunBackendStepInput runBackendStepInput, RunBackendStepOutput runBackendStepOutput) Customization point for subclasses of this step.protected void
preTransform
(List<QRecord> qRecords, RunBackendStepInput runBackendStepInput, RunBackendStepOutput runBackendStepOutput) Customization point for subclasses of this step.void
run
(RunBackendStepInput runBackendStepInput, RunBackendStepOutput runBackendStepOutput) Execute the backend step - using the request as input, and the result as output.
-
Constructor Details
-
StreamedETLBackendStep
public StreamedETLBackendStep()
-
-
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 interfaceBackendStep
- Throws:
QException
-
preTransform
protected void preTransform(List<QRecord> qRecords, RunBackendStepInput runBackendStepInput, RunBackendStepOutput runBackendStepOutput) Customization point for subclasses of this step. -
postTransform
protected void postTransform(List<QRecord> qRecords, RunBackendStepInput runBackendStepInput, RunBackendStepOutput runBackendStepOutput) Customization point for subclasses of this step.
-