Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-6130

Remove references to adding configuration settings to a .properties file

XMLWordPrintable

      Per the comment in [PR 3980|https://github.com/debezium/debezium/pull/3980} for DBZ-5283, when the documentation provides examples for connector property settings, it should refer to the connector configuration and not to a .properties file.
      Similar to the recent changes to the documentation for the ExtractChangedRecordState and MongoDB ExtractNewRecordState SMTs, the configuration examples in the following topics should refer to settings in the connector configuration, and they should not mention the use of a .properties file:

      mongodb-outbox-event-router.adoc:175:
      Basic Debezium MongoDB outbox event router SMT configuration

      To configure a Debezium connector to support the outbox pattern, configure the `outbox.EventRouter` SMT. The following example shows the basic configuration for the SMT in a `.properties` file:

      outbox-event-router.adoc:182:
      Basic Debezium outbox event router SMT configuration

      To configure a Debezium connector to support the outbox pattern, configure the `outbox.EventRouter` SMT. For example, the basic configuration in a `.properties` file looks like this:

      topic-routing.adoc:64:
      Example of routing Debezium records for multiple tables to one topic

      For example, configuration in a `.properties` file looks like this:

      event-flattening.adoc:140:
      Configuration of Debezium event flattening transformation

      Configure the Debezium event flattening SMT in a Kafka Connect source or sink connector by adding the SMT configuration details to your connector's configuration. To obtain the default behavior, in a `.properties` file, you would specify something like the following:

            broldan@redhat.com Robert Roldan
            broldan@redhat.com Robert Roldan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: