[
https://issues.apache.org/jira/browse/NIFI-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539083#comment-16539083
]
ASF GitHub Bot commented on NIFI-5070:
--------------------------------------
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.
> java.sql.SQLException: ERROR 1101 (XCL01): ResultSet is closed
> --------------------------------------------------------------
>
> Key: NIFI-5070
> URL: https://issues.apache.org/jira/browse/NIFI-5070
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Gardella Juan Pablo
> Priority: Major
>
> Discovered during NIFI-5049. According [ResultSet.next()
> javadoc|https://docs.oracle.com/javase/8/docs/api/java/sql/ResultSet.html#next%E2%80%93]:
> _When a call to the {{next}} method returns {{false}}, the cursor is
> positioned after the last row. Any invocation of a {{ResultSet}} method which
> requires a current row will result in a {{SQLException}} being thrown. If the
> result set type is {{TYPE_FORWARD_ONLY}}, it is vendor specified whether
> their JDBC driver implementation will return {{false}} or throw an
> {{SQLException}} on a subsequent call to {{next}}._
> With Phoenix Database and QueryDatabaseTable the exception
> {{java.sql.SQLException: ERROR 1101 (XCL01): ResultSet is closed}} is raised.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
