alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-4012 Suggested changes

Browse Source
This commit is contained in:
Chris Cranford 2021-11-18 14:03:20 -05:00 committed by Gunnar Morling
parent 349b9690f4
commit ab86cd18a9
3 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
debezium-connector-mongodb/src/main/java/io/debezium/connector/mongodb/transforms/outbox/MongoEventRouter.java
View File

@ -23,6 +23,7 @@
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import io.debezium.common.annotation.Incubating;
import io.debezium.config.Configuration;
import io.debezium.connector.mongodb.transforms.ExtractNewDocumentState;
import io.debezium.connector.mongodb.transforms.MongoDataConverter;
@ -36,6 +37,7 @@
*
* @author Sungho Hwang
*/
@Incubating
public class MongoEventRouter<R extends ConnectRecord<R>> implements Transformation<R> {
private static final Logger LOGGER = LoggerFactory.getLogger(MongoEventRouter.class);

4
debezium-core/src/main/java/io/debezium/transforms/outbox/EventRouterConfigDefinition.java
View File

@ -118,11 +118,11 @@ public String getAlias() {
}
public static final Field OPERATION_INVALID_BEHAVIOR = Field.create("table.op.invalid.behavior")
.withDisplayName("Behavior when the route fails to apply")
.withDisplayName("Behavior when capturing an unexpected outbox event")
.withEnum(InvalidOperationBehavior.class, InvalidOperationBehavior.SKIP_AND_WARN)
.withWidth(ConfigDef.Width.MEDIUM)
.withImportance(ConfigDef.Importance.MEDIUM)
.withDescription("While Debezium is capturing changes from the table, it's expecting only to see 'create' row events," +
.withDescription("While Debezium is capturing changes from the outbox table, it is expecting only to process 'create' or 'delete' row events;" +
" in case something else is processed this transform can log it as warning, error or stop the" +
" process.");

6
documentation/modules/ROOT/pages/transformations/mongodb-outbox-event-router.adoc
View File

@ -325,14 +325,14 @@ The following table describes the options that you can specify for the outbox ev
|[[mongodb-outbox-event-router-property-collection-op-invalid-behavior]]<<mongodb-outbox-event-router-property-collection-op-invalid-behavior, `collection.op.invalid.behavior`>>
|`warn`
|Collection
a|Determines the behavior of the SMT when there is an `UPDATE` operation on the outbox collection. Possible settings are:
a|Determines the behavior of the SMT when there is an update operation on the outbox collection. Possible settings are:
* `warn` - The SMT logs a warning and continues to the next outbox collection document.
* `error` - The SMT logs an error and continues to the next outbox collection document.
* `fatal` - The SMT logs an error and the connector stops processing.
All changes in an outbox collection are expected to be `INSERT` operations. That is, an outbox collection functions as a queue; updates to documents in an outbox collection are not allowed.
The SMT automatically filters out `DELETE` operations on an outbox collection.
All changes in an outbox collection are expected to be an insert or delete operation. That is, an outbox collection functions as a queue; updates to documents in an outbox collection are not allowed.
The SMT automatically filters out delete operations (for removing proceeded outbox events) on an outbox collection.
|[[mongodb-outbox-event-router-property-collection-field-event-id]]<<mongodb-outbox-event-router-property-collection-field-event-id, `collection.field.event.id`>>
|`_id`