Striim 3.9.7 documentation

How update and delete operations are handled in writers

In some cases, when the input of a target is the output of a CDC source, Striim can match primary keys or other unique identifiers to replicate source update and delete operations in the target, keeping the source and target in sync.

In other cases, such matching is impossible, so updates and deletes are written as inserts. This is often acceptable when the target is a data warehouse.

With the following source-target combinations, update and delete operations in the source are handled as updates and deletes in the target:

source

target

  • FileReader with GoldengateTrailParser

  • HPNonStop readers

  • MSSQLReader

  • MySQLReader

  • OracleReader

  • PostgreSQLReader

  • SalesforceReader

  • AzureSQLDWHWriter

  • BigQueryWriter (in MERGE mode)

  • CosmosDBWriter

  • DatabaseWriter

  • HazelcastWriter

  • HBaseWriter

  • KuduWriter

  • MapRDBWriter

  • RedshiftWriter

  • SnowflakeWriter

  • SpannerWriter

  • MongoDBReader

  • CosmosDBWriter

With the following source-target combinations, update and delete operations in the source are handled as inserts in the target:

source

target

  • FileReader with GoldengateTrailParser

  • HPNonStop readers

  • MSSQLReader

  • MySQLReader

  • OracleReader

  • PostgreSQLReader

  • SalesforceReader

  • BigQueryWriter (in APPENDONLY mode)

  • ClouderaHiveWriter

  • DatabaseReader

  • IncrementalBatchReader

  • AzureSQLDWHWriter

  • BigQueryWriter

  • CosmosDBWriter

  • DatabaseWriter

  • HazelcastWriter

  • HBaseWriter

  • KuduWriter

  • MapRDBWriter

  • RedshiftWriter

  • SnowflakeWriter

  • SpannerWriter

When the target is HiveWriter or HortonworksHiveWriter, update and delete operations may be handled by the target as updates and deletes or as inserts depending on various factors (see Hive Writer for details).