[
https://issues.apache.org/jira/browse/HIVE-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283758#comment-15283758
]
zhihai xu commented on HIVE-13760:
----------------------------------
thanks [~thejas]! yes, HIVE-4924 should work also. But if we can also support a
config parameter HIVE_QUERY_TIMEOUT, it may give Hive admin more flexibility to
control query for resource saving purpose. This will be a small change based on
HIVE-4924. We can compare function parameter queryTimeout with
HIVE_QUERY_TIMEOUT at SQLOperation and use the smaller one as the real timeout
value, Does it make sense to you? If you agree, I can write a patch for it.
> Add a HIVE_QUERY_TIMEOUT configuration to kill a query if a query is running
> for more than the configured timeout value.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-13760
> URL: https://issues.apache.org/jira/browse/HIVE-13760
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 2.0.0
> Reporter: zhihai xu
>
> Add a HIVE_QUERY_TIMEOUT configuration to kill a query if a query is running
> for more than the configured timeout value. The default value will be -1 ,
> which means no timeout. This will be useful for user to manage queries with
> SLA.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
