[
https://issues.apache.org/jira/browse/PHOENIX-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy Gelhausen updated PHOENIX-2297:
-
Description:
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. 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 PhoenixDriver.
was:
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.
> Support jdbcClient instantiation with timeout param &
> statement.setQueryTimeout method
> --
>
> 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. 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
> PhoenixDriver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
