Class StreamedETLExecuteStep

java.lang.Object
com.kingsrook.qqq.backend.core.processes.implementations.etl.streamedwithfrontend.BaseStreamedETLStep
com.kingsrook.qqq.backend.core.processes.implementations.etl.streamedwithfrontend.StreamedETLExecuteStep
All Implemented Interfaces:
BackendStep

public class StreamedETLExecuteStep extends BaseStreamedETLStep implements BackendStep
Backend step to do the execute portion of a streamed ETL job. Works within a transaction (per the backend module of the destination table).
  • Constructor Details

    • StreamedETLExecuteStep

      public StreamedETLExecuteStep()
  • 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