-
Notifications
You must be signed in to change notification settings - Fork 25k
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
ESQL: connect_transport_exception
should be thrown instead of verification_exception
when ENRICH-ing if remote is disconnected
#119750
Conversation
…_exception` in ENRICH In the context of ENRICH, if a remote is disconnected and skip unavailable is set to `true`, then `verification_exception` is thrown instead of `connect_transport_exception`. This PR fixes this and adds the IT tests for ENRICH for RCS 1 and RCS 2.
verification_exception
is thrown instead of connect_transport_exception
in ENRICH when remote is disconnectedconnect_transport_exception
should be thrown instead of verification_exception
when ENRICH-ing if remote is disconnected
Hi @pawankartik-elastic, I've created a changelog YAML for you. |
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
connect_transport_exception
should be thrown instead of verification_exception
when ENRICH-ing if remote is disconnectedconnect_transport_exception
should be thrown instead of verification_exception
when ENRICH-ing if remote is disconnected
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Note : I adjusted the title and the changelog to start with "ESQL", as that's the format ESQL wants for the release notes. I also adjusted the v8.17.0 label v8.17.2, as you want to target the next release in the autobackport.
…fication_exception` when ENRICH-ing if remote is disconnected (elastic#119750) * fix: `verification_exception` is thrown instead of `connect_transport_exception` in ENRICH In the context of ENRICH, if a remote is disconnected and skip unavailable is set to `true`, then `verification_exception` is thrown instead of `connect_transport_exception`. This PR fixes this and adds the IT tests for ENRICH for RCS 1 and RCS 2. * Update docs/changelog/119750.yaml * Update 119750.yaml --------- Co-authored-by: Michael Peterson <[email protected]>
…fication_exception` when ENRICH-ing if remote is disconnected (elastic#119750) * fix: `verification_exception` is thrown instead of `connect_transport_exception` in ENRICH In the context of ENRICH, if a remote is disconnected and skip unavailable is set to `true`, then `verification_exception` is thrown instead of `connect_transport_exception`. This PR fixes this and adds the IT tests for ENRICH for RCS 1 and RCS 2. * Update docs/changelog/119750.yaml * Update 119750.yaml --------- Co-authored-by: Michael Peterson <[email protected]>
…fication_exception` when ENRICH-ing if remote is disconnected (#119750) (#119881) * fix: `verification_exception` is thrown instead of `connect_transport_exception` in ENRICH In the context of ENRICH, if a remote is disconnected and skip unavailable is set to `true`, then `verification_exception` is thrown instead of `connect_transport_exception`. This PR fixes this and adds the IT tests for ENRICH for RCS 1 and RCS 2. * Update docs/changelog/119750.yaml * Update 119750.yaml --------- Co-authored-by: Michael Peterson <[email protected]>
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.