[jira] [Commented] (HIVE-3596) Regression - HiveConf static variable causes issues in long running JVM instances with /tmp/ data

["Chris McConnell (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480209#comment-13480209 ] 

Chris McConnell commented on HIVE-3596:
---------------------------------------

Review: https://reviews.facebook.net/D6093 
                
> Regression - HiveConf static variable causes issues in long running JVM instances with /tmp/ data
> -------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-3596
>                 URL: https://issues.apache.org/jira/browse/HIVE-3596
>             Project: Hive
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 0.8.0, 0.8.1, 0.9.0
>            Reporter: Chris McConnell
>             Fix For: 0.8.1, 0.9.0, 0.10.0
>
>         Attachments: HIVE-3596.patch
>
>
> With Hive 0.8.x, HiveConf was changed to utilize the private, static member "confVarURL" which points to /tmp/hive-<user>-<tmp_number>.xml for job configuration settings. 
> During long running JVMs, such as a Beeswax server, which creates multiple HiveConf objects over time this variable does not properly get updated between jobs and can cause job failure if the OS cleans /tmp/ during a cron job. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira