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

abris #230 improve exception message and comments #231

Merged
merged 2 commits into from
Jul 29, 2021

Conversation

cerveada
Copy link
Collaborator

No description provided.

@cerveada cerveada linked an issue Jul 13, 2021 that may be closed by this pull request
@cerveada
Copy link
Collaborator Author

I removed SchemaManagerException. It causes the binary incompatibility errors, but it is not used anywhere, so I would delete it.

At the end I kept the condition as is, seems to me, it is not better reversed more like the same.

@kevinwallimann
Copy link
Collaborator

kevinwallimann commented Jul 14, 2021

I removed SchemaManagerException. It causes the binary incompatibility errors, but it is not used anywhere, so I would delete it.

At the end I kept the condition as is, seems to me, it is not better reversed more like the same.

I agree with that. The logic is not confusing, only the error message was. "Make sure that the Schema Registry is available, the parameters are correct" This part suggested that schema registry being unavailable could be the cause, which cannot be.

Unfortunately I think you cannot remove the SchemaManagerException due to binary compatibility reasons.

@cerveada
Copy link
Collaborator Author

Unfortunately I think you cannot remove the SchemaManagerException due to binary compatibility reasons.

Are you afraid someone is catching it even though we never throw it?
If we want to be extra safe, we can keep it for that case.

@kevinwallimann
Copy link
Collaborator

Unfortunately I think you cannot remove the SchemaManagerException due to binary compatibility reasons.

Are you afraid someone is catching it even though we never throw it?
If we want to be extra safe, we can keep it for that case.

No, I don't think anybody would do that. Then again, you never know. It's more a question of principles, whether we strictly adhere to binary compatibility and defer all incompatible changes to the next major version or we define a gray area where we accept incompatible changes. Probably we should first implement #159

@cerveada cerveada merged commit 2b217be into master Jul 29, 2021
@kevinwallimann kevinwallimann deleted the bugfix/abris-230-improve-exception-message branch February 1, 2022 15:00
gintautassulskus-elsevier pushed a commit to gintautassulskus-elsevier/ABRiS that referenced this pull request Feb 4, 2022
* abris AbsaOSS#230 improve exception message and comments

* abris AbsaOSS#230 deprecate unused Exception
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve exceptions during schema register
3 participants