You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Randy Gelhausen (JIRA)" <ji...@apache.org> on 2015/09/30 22:51:04 UTC

[jira] [Created] (PHOENIX-2297) Support standard jdbc setTimeout call

Randy Gelhausen created PHOENIX-2297:
----------------------------------------

             Summary: Support standard jdbc setTimeout call
                 Key: PHOENIX-2297
                 URL: https://issues.apache.org/jira/browse/PHOENIX-2297
             Project: Phoenix
          Issue Type: Improvement
            Reporter: Randy Gelhausen


When using Phoenix with Storm's JDBCInsertBolt or NiFi's ExecuteSQL processor, the default timeout settings cause Phoenix statements to fail.

With JDBCInsertBolt and JDBCLookupBolt, I've had to set query timeout seconds to -1 to get Phoenix statements working at all. Storm creates a JDBC client with the standard "new JdbcClient(connectionProvider, queryTimeoutSecs)" call.

NiFi's ExecuteSQL processor sets a timeout on every statement: "statement.setQueryTimeout(queryTimeout)".

Both of these seem to be standard JDBC usage, but fail when using Phoenix's JDBC client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)