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

When using `skip.messages.without.change=true` a WARN log message is reported for each record


    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 2.4.0.Beta1
    • None
    • core-library
    • None
    • False
    • None
    • False

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Feature request or enhancement

      Which use case/requirement will be addressed by the proposed feature?

      Currently, each skipped change event yields a WARN log message. This both pollutes the log and also exposes sensitive data

      Implementation ideas (optional)

      Change log message level to DEBUG

            Unassigned Unassigned
            zalmane Oren Elias (Inactive)
            Sergey Eizner
            0 Vote for this issue
            4 Start watching this issue