[ 
https://issues.apache.org/jira/browse/TRAFODION-3331?focusedWorklogId=325330&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325330
 ]

ASF GitHub Bot logged work on TRAFODION-3331:
---------------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Oct/19 21:05
            Start Date: 08/Oct/19 21:05
    Worklog Time Spent: 10m 
      Work Description: selvaganesang commented on pull request #1861: 
[TRAFODION-3331] JDBC T4 driver to support login timeout and query timeout
URL: https://github.com/apache/trafodion/pull/1861
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 325330)
    Time Spent: 40m  (was: 0.5h)

> JDBC T4 driver to support login timeout  and query timeout 
> -----------------------------------------------------------
>
>                 Key: TRAFODION-3331
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-3331
>             Project: Apache Trafodion
>          Issue Type: Bug
>            Reporter: Selvaganesan Govindarajan
>            Assignee: Selvaganesan Govindarajan
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> JDBC T4 driver lacks in functionality to support login timeout and query 
> timeout.  In addition the query timeout needs to sync up with cancelling 
> query functionality in Trafodion SQL engine. It is possible that graceful 
> query cancel is disabled in the Trafodion SQL engine. In that the process 
> that executes the query will be killed abruptly. In that case, query timeout 
> needs to tolerated till the query is active for some time before it can be 
> cancelled. This will avoid disruption to connection and hence normal 
> functioning of the application



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to