Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Risingwave doesn't throw error when server.id in mysql cdc is incorrect. #12025

Closed
liurenjie1024 opened this issue Sep 1, 2023 · 4 comments
Closed
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@liurenjie1024
Copy link
Contributor

Describe the bug

When creating a mysql cdc table, user fills in an incorrect server.id, risingwave failed silently in background, but didn't report any error.

Error message/log

No response

To Reproduce

No response

Expected behavior

It's expected to report this error to user explicitly when server.id is misconfigured rather forcing user to find it in connector log.

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

@hzxa21
Copy link
Collaborator

hzxa21 commented Oct 10, 2023

@StrikeW Any updates?

@StrikeW StrikeW modified the milestones: release-1.3, release-1.4 Oct 10, 2023
@StrikeW
Copy link
Contributor

StrikeW commented Oct 10, 2023

@StrikeW Any updates?

No yet.

@StrikeW
Copy link
Contributor

StrikeW commented Oct 26, 2023

#13031 (comment)

@hzxa21
Copy link
Collaborator

hzxa21 commented Nov 8, 2023

Done by #13031

@hzxa21 hzxa21 closed this as completed Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants