Class StreamedETLPreviewStep

java.lang.Object

com.kingsrook.qqq.backend.core.processes.implementations.etl.streamedwithfrontend.BaseStreamedETLStep

com.kingsrook.qqq.backend.core.processes.implementations.etl.streamedwithfrontend.StreamedETLPreviewStep

All Implemented Interfaces:

BackendStep

public class StreamedETLPreviewStep
extends BaseStreamedETLStep
implements BackendStep

Backend step to do a preview of a full streamed ETL job

Field Summary

Fields inherited from class com.kingsrook.qqq.backend.core.processes.implementations.etl.streamedwithfrontend.BaseStreamedETLStep

PROCESS_OUTPUT_RECORD_LIST_LIMIT

Constructor Summary

Constructors

Constructor	Description
StreamedETLPreviewStep()

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.

Methods inherited from class com.kingsrook.qqq.backend.core.processes.implementations.etl.streamedwithfrontend.BaseStreamedETLStep

getExtractStep, getLoadStep, getTransformStep, moveReviewStepAfterValidateStep, updateRecordsWithDisplayValuesAndPossibleValues

Methods inherited from class java.lang.Object

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

Constructor Details

StreamedETLPreviewStep

public StreamedETLPreviewStep()

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