[
https://issues.apache.org/jira/browse/PHOENIX-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277418#comment-14277418
]
James Taylor commented on PHOENIX-1582:
---------------------------------------
Good idea, [~salperwy]. This would not be difficult and would be a good
contribution for a newbie. Take a look at BaseResultIterators.getIterators(),
line 519:
{code}
int queryTimeOut = props.getInt(QueryServices.THREAD_TIMEOUT_MS_ATTRIB,
DEFAULT_THREAD_TIMEOUT_MS);
{code}
This determines the timeout for a query. You'd need to instead get the timeout
through PhoenixStatement, like this:
{code}
int queryTimeOut = context.getStatement().getQueryTimeout();
{code}
In PhoenixStatement, you'd add a new member variable for queryTimeout which
would default to what we're currently using as the queryTimeOut above.
> Support TimeOut in JDBC
> -----------------------
>
> Key: PHOENIX-1582
> URL: https://issues.apache.org/jira/browse/PHOENIX-1582
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.2, 3.2
> Reporter: Christophe S
>
> Some tools as JMeter need the Timeout function in the JDBC driver to be
> implemented in order to work.
> Would it be possible to implement this function?
> Thx!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
