cdc: issue a warning when a duplicate changefeed is created #144262
Assignees
Labels
A-cdc
Change Data Capture
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-cdc
Comments
|
cc @cockroachdb/cdc |
log-head
added a commit
to log-head/cockroach
that referenced
this issue
May 15, 2025
Previously, although it is possible for changefeeds to be created with the same destination URI, in some cases this is due to an error or typo that can be hard to detect, and can cause issues in the downstream environment. To address this, this patch issues a wawning when a changefeed is created for the same tables and same URI. The warning looks like: NOTICE: You have created a duplicate changefeed Fixes: cockroachdb#144262 Epic: CRDB-49296 Release note (general change): Provide a warning when creating a changefeed that already exists
log-head
added a commit
to log-head/cockroach
that referenced
this issue
May 15, 2025
Previously, although it is possible for changefeeds to be created with the same destination URI, in some cases this is due to an error or typo that can be hard to detect, and can cause issues in the downstream environment. To address this, this patch issues a wawning when a changefeed is created for the same tables and same URI. The warning looks like: NOTICE: You have created a duplicate changefeed Fixes: cockroachdb#144262 Epic: CRDB-49296 Release note (general change): Provide a warning when creating a changefeed that already exists
log-head
added a commit
to log-head/cockroach
that referenced
this issue
May 19, 2025
Previously, although it is possible for changefeeds to be created with the same destination URI, in some cases this is due to an error or typo that can be hard to detect, and can cause issues in the downstream environment. To address this, this patch issues a wawning when a changefeed is created for the same tables and same URI. The warning looks like: NOTICE: You have created a duplicate changefeed Fixes: cockroachdb#144262 Epic: CRDB-49296 Release note (general change): Provide a warning when creating a changefeed that already exists
log-head
added a commit
to log-head/cockroach
that referenced
this issue
May 19, 2025
Previously, although it is possible for changefeeds to be created with the same destination URI, in some cases this is due to an error or typo that can be hard to detect, and can cause issues in the downstream environment. To address this, this patch issues a wawning when a changefeed is created for the same tables and same URI. The warning looks like: NOTICE: You have created a duplicate changefeed Fixes: cockroachdb#144262 Epic: CRDB-49296 Release note (general change): Provide a warning when creating a changefeed that already exists
log-head
added a commit
to log-head/cockroach
that referenced
this issue
May 20, 2025
Previously, although it is possible for changefeeds to be created with the same destination URI, in some cases this is due to an error or typo that can be hard to detect, and can cause issues in the downstream environment. To address this, this patch issues a wawning when a changefeed is created for the same tables and same URI. The warning looks like: NOTICE: You have created a duplicate changefeed Fixes: cockroachdb#144262 Epic: CRDB-49296 Release note (general change): Provide a warning when creating a changefeed that already exists
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Although it is possible for changefeeds to be created with the same destination URI, in some cases this is due to an error or typo that can be hard to detect, and can cause issues in the downstream environment. We should issue a warning when changefeeds are created for the same tables and same URI to alert users when this happens.
Jira issue: CRDB-49296
The text was updated successfully, but these errors were encountered: