ESQL: connect_transport_exception
should be thrown instead of verification_exception
when ENRICH-ing if remote is disconnected
#119750
+743
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this fix,
VerificationException
is thrown if a remote is disconnected and skip unavailable istrue
duringENRICH
-ing. This is not what we want. It is expected that aConnectTransportException
be thrown instead. This PR fixes it so that aConnectTransportException
is thrown and additionally addsENRICH
tests for RCS 1 and RCS 2.