Interface BackendStep

All Known Implementing Classes:
AbstractExtractStep, BasicETLCleanupSourceFilesStep, BasicETLCollectSourceFileNamesStep, BasicETLExtractFunction, BasicETLLoadFunction, BasicETLTransformFunction, BulkInsertExtractStep, BulkInsertPrepareFileMappingStep, BulkInsertPrepareFileUploadStep, BulkInsertPrepareValueMappingStep, BulkInsertReceiveFileMappingStep, BulkInsertReceiveValueMappingStep, ColumnStatsStep, DeleteSavedBulkLoadProfileProcess, DeleteSavedViewProcess, DeleteSharedRecordProcess, DynamicSiteProcessStep, EditSharedRecordProcess, ExecuteReportStep, ExtractViaBasepullQueryStep, ExtractViaQueryStep, FilesystemImporterStep, FilesystemSyncStep, GarbageCollectorExtractStep, GetSharedRecordsProcess, HealBadRecordAutomationStatusesProcessStep, InsertSharedRecordProcess, LoadInitialRecordsStep, LoadScriptTestDetailsProcessStep, MockBackendStep, PauseAllQuartzJobsProcess, PrepareReportForRecordStep, PrepareReportStep, QuerySavedBulkLoadProfileProcess, QuerySavedViewProcess, RenderSavedReportExecuteStep, RenderSavedReportPreStep, RescheduleAllJobsProcess, ResumeAllQuartzJobsProcess, RunRecordScriptExtractStep, RunScheduledReportExecuteStep, RunTableAutomationsProcessStep, SampleMetaDataProvider.SleeperStep, SampleMetaDataProvider.ThrowerStep, ScheduleAllNewJobsProcess, StoreSavedBulkLoadProfileProcess, StoreSavedViewProcess, StoreScriptRevisionProcessStep, StreamedETLBackendStep, StreamedETLExecuteStep, StreamedETLFilesystemBackendStep, StreamedETLPreviewStep, StreamedETLValidateStep, TestScriptProcessStep, UnscheduleAllJobsProcess
public interface BackendStep
Simple interface that Backend Steps (e.g., code within processes) must implement

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

  • Method Details

    • run

      void run(RunBackendStepInput runBackendStepInput, RunBackendStepOutput runBackendStepOutput) throws QException
      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