Interface StartReplicationTaskRequest.Builder

All Superinterfaces:
AwsRequest.Builder, Buildable, CopyableBuilder<StartReplicationTaskRequest.Builder,StartReplicationTaskRequest>, DatabaseMigrationRequest.Builder, SdkBuilder<StartReplicationTaskRequest.Builder,StartReplicationTaskRequest>, SdkPojo, SdkRequest.Builder
Enclosing class:
StartReplicationTaskRequest
@Mutable @NotThreadSafe public static interface StartReplicationTaskRequest.Builder extends DatabaseMigrationRequest.Builder, SdkPojo, CopyableBuilder<StartReplicationTaskRequest.Builder,StartReplicationTaskRequest>

  • Method Details

    • replicationTaskArn

      StartReplicationTaskRequest.Builder replicationTaskArn(String replicationTaskArn)

      The Amazon Resource Name (ARN) of the replication task to be started.

      Parameters:
      replicationTaskArn - The Amazon Resource Name (ARN) of the replication task to be started.
      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • startReplicationTaskType

      StartReplicationTaskRequest.Builder startReplicationTaskType(String startReplicationTaskType)

      The type of replication task to start.

      start-replication is the only valid action that can be used for the first time a task with the migration type of full-loadfull-load, full-load-and-cdc or cdc is run. Any other action used for the first time on a given task, such as resume-processing and reload-target will result in data errors.

      You can also use ReloadTables to reload specific tables that failed during migration instead of restarting the task.

      For a full-load task, the resume-processing option will reload any tables that were partially loaded or not yet loaded during the full load phase.

      For a full-load-and-cdc task, DMS migrates table data, and then applies data changes that occur on the source. To load all the tables again, and start capturing source changes, use reload-target. Otherwise use resume-processing, to replicate the changes from the last stop position.

      For a cdc only task, to start from a specific position, you must use start-replication and also specify the start position. Check the source endpoint DMS documentation for any limitations. For example, not all sources support starting from a time.

      resume-processing is only available for previously executed tasks.

      Parameters:
      startReplicationTaskType - The type of replication task to start.

      start-replication is the only valid action that can be used for the first time a task with the migration type of full-loadfull-load, full-load-and-cdc or cdc is run. Any other action used for the first time on a given task, such as resume-processing and reload-target will result in data errors.

      You can also use ReloadTables to reload specific tables that failed during migration instead of restarting the task.

      For a full-load task, the resume-processing option will reload any tables that were partially loaded or not yet loaded during the full load phase.

      For a full-load-and-cdc task, DMS migrates table data, and then applies data changes that occur on the source. To load all the tables again, and start capturing source changes, use reload-target. Otherwise use resume-processing, to replicate the changes from the last stop position.

      For a cdc only task, to start from a specific position, you must use start-replication and also specify the start position. Check the source endpoint DMS documentation for any limitations. For example, not all sources support starting from a time.

      resume-processing is only available for previously executed tasks.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:

    • startReplicationTaskType

      StartReplicationTaskRequest.Builder startReplicationTaskType(StartReplicationTaskTypeValue startReplicationTaskType)

      The type of replication task to start.

      start-replication is the only valid action that can be used for the first time a task with the migration type of full-loadfull-load, full-load-and-cdc or cdc is run. Any other action used for the first time on a given task, such as resume-processing and reload-target will result in data errors.

      You can also use ReloadTables to reload specific tables that failed during migration instead of restarting the task.

      For a full-load task, the resume-processing option will reload any tables that were partially loaded or not yet loaded during the full load phase.

      For a full-load-and-cdc task, DMS migrates table data, and then applies data changes that occur on the source. To load all the tables again, and start capturing source changes, use reload-target. Otherwise use resume-processing, to replicate the changes from the last stop position.

      For a cdc only task, to start from a specific position, you must use start-replication and also specify the start position. Check the source endpoint DMS documentation for any limitations. For example, not all sources support starting from a time.

      resume-processing is only available for previously executed tasks.

      Parameters:
      startReplicationTaskType - The type of replication task to start.

      start-replication is the only valid action that can be used for the first time a task with the migration type of full-loadfull-load, full-load-and-cdc or cdc is run. Any other action used for the first time on a given task, such as resume-processing and reload-target will result in data errors.

      You can also use ReloadTables to reload specific tables that failed during migration instead of restarting the task.

      For a full-load task, the resume-processing option will reload any tables that were partially loaded or not yet loaded during the full load phase.

      For a full-load-and-cdc task, DMS migrates table data, and then applies data changes that occur on the source. To load all the tables again, and start capturing source changes, use reload-target. Otherwise use resume-processing, to replicate the changes from the last stop position.

      For a cdc only task, to start from a specific position, you must use start-replication and also specify the start position. Check the source endpoint DMS documentation for any limitations. For example, not all sources support starting from a time.

      resume-processing is only available for previously executed tasks.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:

    • cdcStartTime

      StartReplicationTaskRequest.Builder cdcStartTime(Instant cdcStartTime)

      Indicates the start time for a change data capture (CDC) operation. Use either CdcStartTime or CdcStartPosition to specify when you want a CDC operation to start. Specifying both values results in an error.

      Timestamp Example: --cdc-start-time “2018-03-08T12:12:12”

      Parameters:
      cdcStartTime - Indicates the start time for a change data capture (CDC) operation. Use either CdcStartTime or CdcStartPosition to specify when you want a CDC operation to start. Specifying both values results in an error.

      Timestamp Example: --cdc-start-time “2018-03-08T12:12:12”

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • cdcStartPosition

      StartReplicationTaskRequest.Builder cdcStartPosition(String cdcStartPosition)

      Indicates when you want a change data capture (CDC) operation to start. Use either CdcStartPosition or CdcStartTime to specify when you want a CDC operation to start. Specifying both values results in an error.

      The value can be in date, checkpoint, or LSN/SCN format.

      Date Example: --cdc-start-position “2018-03-08T12:12:12”

      Checkpoint Example: --cdc-start-position "checkpoint:V1#27#mysql-bin-changelog.157832:1975:-1:2002:677883278264080:mysql-bin-changelog.157832:1876#0#0#*#0#93"

      LSN Example: --cdc-start-position “mysql-bin-changelog.000024:373”

      When you use this task setting with a source PostgreSQL database, a logical replication slot should already be created and associated with the source endpoint. You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot. For more information, see Extra Connection Attributes When Using PostgreSQL as a Source for DMS.

      Parameters:
      cdcStartPosition - Indicates when you want a change data capture (CDC) operation to start. Use either CdcStartPosition or CdcStartTime to specify when you want a CDC operation to start. Specifying both values results in an error.

      The value can be in date, checkpoint, or LSN/SCN format.

      Date Example: --cdc-start-position “2018-03-08T12:12:12”

      Checkpoint Example: --cdc-start-position "checkpoint:V1#27#mysql-bin-changelog.157832:1975:-1:2002:677883278264080:mysql-bin-changelog.157832:1876#0#0#*#0#93"

      LSN Example: --cdc-start-position “mysql-bin-changelog.000024:373”

      When you use this task setting with a source PostgreSQL database, a logical replication slot should already be created and associated with the source endpoint. You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot. For more information, see Extra Connection Attributes When Using PostgreSQL as a Source for DMS.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • cdcStopPosition

      StartReplicationTaskRequest.Builder cdcStopPosition(String cdcStopPosition)

      Indicates when you want a change data capture (CDC) operation to stop. The value can be either server time or commit time.

      Server time example: --cdc-stop-position “server_time:2018-02-09T12:12:12”

      Commit time example: --cdc-stop-position “commit_time:2018-02-09T12:12:12“

      Parameters:
      cdcStopPosition - Indicates when you want a change data capture (CDC) operation to stop. The value can be either server time or commit time.

      Server time example: --cdc-stop-position “server_time:2018-02-09T12:12:12”

      Commit time example: --cdc-stop-position “commit_time:2018-02-09T12:12:12“

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • overrideConfiguration

      StartReplicationTaskRequest.Builder overrideConfiguration(AwsRequestOverrideConfiguration overrideConfiguration)
      Description copied from interface: AwsRequest.Builder
      Add an optional request override configuration.
      Specified by:
      overrideConfiguration in interface AwsRequest.Builder
      Parameters:
      overrideConfiguration - The override configuration.
      Returns:
      This object for method chaining.

    • overrideConfiguration

      StartReplicationTaskRequest.Builder overrideConfiguration(Consumer<AwsRequestOverrideConfiguration.Builder> builderConsumer)
      Description copied from interface: AwsRequest.Builder
      Add an optional request override configuration.
      Specified by:
      overrideConfiguration in interface AwsRequest.Builder
      Parameters:
      builderConsumer - A Consumer to which an empty AwsRequestOverrideConfiguration.Builder will be given.
      Returns:
      This object for method chaining.