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

Incorrect loading of LSN from offsets

    XMLWordPrintable

Details

    Description

      The code reads LAST_COMPLETELY_PROCESSED_LSN_KEY twice and stores it in both lastCompletelyProcessedLsn and lastCommitLsn.

      It is not clear whether this is intentional or is a bug. If intentional we need to document that fact in the code.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. DBZ-5031 Debezium has never found starting LSN

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. DBZ-4865 Debezium using Postgres connector stuck in infinite loop after auto restart on error

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jpechane Jiri Pechanec
              jpechane Jiri Pechanec
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: