Github user gardellajuanpablo commented on the issue:
https://github.com/apache/nifi/pull/2629
Hi @patricker,
Regarding:
"Also, this seems to specifically be for Phoenix. With the fix as is, I
don't know if it's possible to tell the difference between a database going
offline for maintenance mid resultset read and a Phoenix end of resulset
closure."
I discovered by using Phoenix, but Phoenix follows the JDBC spec. As I
implemented, if there is a DB error the original exception is propagated to the
caller. Please refer to the change I've did, if I'm missing something, please
let me know.
---
