Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
1
Description
If the connector is stopped and the source bucket is flushed, the connector ignores modifications to the bucket until the sequence numbers catch up to where they were before the bucket was flushed. This is because the "current state" doesn't take into account changes to the vbucket uuid.
Attachments
Issue Links
- depends on
-
KAFKAC-118 Source: vBucketUuid may be incorrect
- Resolved
- duplicates
-
KAFKAC-161 Source: Should include vBucket UUID in saved offset
- Resolved