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

Disallow connector to be registered if another one exists with the same database.server.name exists #83

Open
vaibhav-yb opened this issue Nov 18, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request priority/low Low prioroty issue

Comments

@vaibhav-yb
Copy link
Collaborator

vaibhav-yb commented Nov 18, 2022

Since the database.server.name is the logical name for the connector, it has to be unique across all the deployed connectors.

The problem currently from the user's perspective is that they may end up deploying connectors with same database.server.name - to tackle this, see if the mechanism can be implemented where we disallow the connector deployment if another connector with the same database.server.name exists in the Kafka Connect environment.

@vaibhav-yb vaibhav-yb self-assigned this Nov 18, 2022
@vaibhav-yb vaibhav-yb added enhancement New feature or request priority/low Low prioroty issue priority/medium Medium priority issue priority/high High priority issue and removed priority/high High priority issue priority/low Low prioroty issue labels Nov 18, 2022
@vaibhav-yb vaibhav-yb added priority/low Low prioroty issue and removed priority/medium Medium priority issue labels Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority/low Low prioroty issue
Projects
None yet
Development

No branches or pull requests

1 participant