You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenSearch\Common\Exceptions namespace is now marked as deprecated, but they are not thrown at all. OpenSearch\Exception are thrown instead.
It breaks the contract in the minor release of the library and should be a part of the major release. First, deprecate then remove in the upcoming major release.
How can one reproduce the bug?
Catch errors thrown by the 2.3.x release and then upgrade to 2.4.x
What is the expected behavior?
OpenSearch\Common\Exceptions should still be used and removed in the 3.0 release
The text was updated successfully, but these errors were encountered:
We've tried to keep legacy code throwing the legacy exceptions. For clients created using ClientBuilder, Transport and Connection objects, they should throw the same exceptions as per 2.3.x.
Let us know if you have specific examples which are causing you problems.
What is the bug?
OpenSearch\Common\Exceptions
namespace is now marked as deprecated, but they are not thrown at all.OpenSearch\Exception
are thrown instead.It breaks the contract in the minor release of the library and should be a part of the major release. First, deprecate then remove in the upcoming major release.
How can one reproduce the bug?
Catch errors thrown by the 2.3.x release and then upgrade to 2.4.x
What is the expected behavior?
OpenSearch\Common\Exceptions
should still be used and removed in the 3.0 releaseThe text was updated successfully, but these errors were encountered: