Gcp timeout exception search (GONRG-2509)
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
It returns 500.
What is the new/expected behavior?
Added java.net.SocketTimeoutException during search. It will return 408 instead of 500.
Any other useful information
Edited by Riabokon Stanislav(EPAM)[GCP]