Github user patricker commented on the issue:
https://github.com/apache/nifi/pull/2629
I like the unit tests, but what about moving your check?
If you created a `catch` block at the end of the existing `try` block in
`convertToAvroStream` it would probably simplify the flow a lot. Keep the same
`isClosed` check... maybe?
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.
Could we check the Exception Message for the specific Phoenix error code so
we don't block visibility to legitimate early connection closure errors?
---
