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
Remove ElasticsearchIllegalArgumentException
and ElasticsearchIllegalStateException
in favor of the JDK one
#10794
Comments
@s1monw can we remove |
IMO we can |
Could we have any issue with the transport layer if we change the JDK version and if JDK does not serialize the same way those exceptions? |
@dadoonet that makes no difference we also use the same serialization no matter if the exception is in our code or not. |
This commit removes ElasticsearchIAE and ElasticsearchISE in favor of the JDKs IAE and ISE. Closes elastic#10794
This commit removes ElasticsearchIAE and ElasticsearchISE in favor of the JDKs IAE and ISE. Closes elastic#10794
This commit removes ElasticsearchIAE and ElasticsearchISE in favor of the JDKs IAE and ISE. Closes elastic#10794
This commit removes ElasticsearchIAE and ElasticsearchISE in favor of the JDKs IAE and ISE. Closes elastic#10794
…galStateException` in favor of the JDK one Related to elastic/elasticsearch#10794 Closes #204.
…galStateException` in favor of the JDK one Related to elastic/elasticsearch#10794 Closes #82.
…galStateException` in favor of the JDK one Related to elastic/elasticsearch#10794 Closes #51.
…galStateException` in favor of the JDK one Related to elastic/elasticsearch#10794 Closes #41.
…galStateException` in favor of the JDK one Related to elastic/elasticsearch#10794 Closes #50.
These exceptions are obsolete and our REST layer handles the response code just fine now.
The text was updated successfully, but these errors were encountered: