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

Slowness in FieldRenamesTest

    XMLWordPrintable

Details

    Description

      Some methods in FieldRenamesTest assert the absence of records, due to incorrect configuration being given, e.g. shouldNotRenameNestedFieldsToExistingNamesForInsertEvent. They each run about 15 sec, because that's the default timeout for getting records from the test topic, before passing with the assertion on 0 records being available.

      That's rather inefficient and we don't really need to assert those non-available records (which cannot be 100% safe anyways). There's already an assertion on the expected error message in the logs, and additionally we should assert that the connector is in FAILED state. The affected tests can be identified by their duration of ~15 sec each.

      Attachments

        Activity

          People

            ccranfor@redhat.com Chris Cranford
            gmorling@redhat.com Gunnar Morling
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: