Class BulkInsertExtractStep

java.lang.Object

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

com.kingsrook.qqq.backend.core.processes.implementations.bulk.insert.BulkInsertExtractStep

All Implemented Interfaces:

BackendStep

public class BulkInsertExtractStep
extends AbstractExtractStep

Extract step for generic table bulk-insert ETL process This step does a little bit of transforming, actually - taking rows from an uploaded file, and potentially merging them (for child-table use-cases) and applying the "Mapping" - to put fully built records into the pipe for the Transform step.

Constructor Summary

Constructors

Constructor	Description
BulkInsertExtractStep()

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.AbstractExtractStep

createRecordPipe, doCount, getLimit, getRecordPipe, preRun, setLimit, setRecordPipe

Methods inherited from class java.lang.Object

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

Constructor Details

BulkInsertExtractStep

public BulkInsertExtractStep()

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?

Throws:

QException