OptionalcheckMethod used to do consistency checks for read operations. After a read operation, during which both data sources are read from, a check of read consistency may be done using this method.
OptionalerrorConfigure the error tracking for the migration.
Defaults to true.
OptionalexecutionConfigure how the migration should execute. If omitted the execution will be concurrent.
OptionallatencyConfigure the latency tracking for the migration.
Defaults to true.
Implementation which provides a read from the "new" source.
Users are required to provide two different read methods -- one to read from the old migration source, and one to
read from the new source. Additionally, customers can opt-in to consistency tracking by providing a check
function.
Depending on the migration stage, one or both of these read methods may be called.
Throwing an exception from this method will be treated as an error.
Optionalpayload: TMigrationReadInput
An optional payload. The payload is provided when calling the read method on the migration.
The result of the operation. Use LDMigrationSuccess or LDMigrationError to create a suitable return value.
Implementation which provides a read from the "old" source.
Users are required to provide two different read methods -- one to read from the old migration source, and one to
read from the new source. Additionally, customers can opt-in to consistency tracking by providing a check
function.
Depending on the migration stage, one or both of these read methods may be called.
Throwing an exception from this method will be treated as an error.
Implementation which provides a write to the "new" source.
Users are required to provide two different write methods -- one to write to the old migration source, and one to write to the new source. Not every stage requires
Depending on the migration stage, one or both of these write methods may be called.
Throwing an exception from this method will be treated as an error.
Optionalpayload: TMigrationWriteInput
An optional payload. The payload is provided when calling the read method on the migration.
The result of the operation. Use LDMigrationSuccess or LDMigrationError to create a suitable return value.
Implementation which provides a write to the "old" source.
Users are required to provide two different write methods -- one to write to the old migration source, and one to write to the new source. Not every stage requires
Depending on the migration stage, one or both of these write methods may be called.
Throwing an exception from this method will be treated as an error.
Optionalpayload: TMigrationWriteInput
An optional payload. The payload is provided when calling the read method on the migration.
The result of the operation. Use LDMigrationSuccess or LDMigrationError to create a suitable return value.
Configuration for a migration.