-
Notifications
You must be signed in to change notification settings - Fork 76
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
Conversation
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. |
Are you afraid someone is catching it even though we never throw it? |
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 |
* abris AbsaOSS#230 improve exception message and comments * abris AbsaOSS#230 deprecate unused Exception
No description provided.