• Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 2.5.0.Alpha1
    • None
    • core-library
    • None

      ElapsedTimeStrategy::hasElapsed is confusing for variety of reasons:

      • creating ElapsedTimeStrategy is incomplete if it's not followed by calling hasElapsed
      • it doesn't do any wait, while one may can expect it does
      • the main task is actually it's side effect to set new upper time limit for the strategy

      Refactor it to avoid side affects.

            [DBZ-6778] Refactor ElapsedTimeStrategy

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Red Hat build of Debezium 2.5.4 release), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHEA-2024:1726

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Red Hat build of Debezium 2.5.4 release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2024:1726

            Released

            Debezium Builder added a comment - Released

              vjuranek@redhat.com Vojtech Juranek
              vjuranek@redhat.com Vojtech Juranek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: