hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <>
Subject [jira] Commented: (HIVE-1837) optional timeout for hive clients
Date Wed, 08 Dec 2010 02:23:03 GMT


Ashutosh Chauhan commented on HIVE-1837:

One way to get around System.exit() problem in testcase is to create your own SecurityManager
and use that. In your SecurityManager override checkExit() and throw an exception. This way
whenever System.exit() is encountered, an exception will be thrown. In your testcase you can
catch the exception and then do the asserts that you want. I did very similar things while
writing junit tests for Howl. 

> optional timeout for hive clients
> ---------------------------------
>                 Key: HIVE-1837
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Namit Jain
>            Assignee: He Yongqiang
>         Attachments: hive-1837.1.patch, hive-1837.2.patch
> It would be a good idea to have a optional timeout for hive clients.
> We encountered a query today, which seemed to have run by mistake, and it was running
for about a month.
> This was holding zookeeper locks, and making the whole debugging more complex than it
should be.
> It would be a good idea to have a timeout for a hive client.
> @Ning, I remember there was some issue with the Hive client having a timeout of 1 day
with HiPal.
> Do you remember the details ?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message