[
https://issues.apache.org/jira/browse/HIVE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Steinbach updated HIVE-3596:
---------------------------------
Status: Open (was: Patch Available)
Looks like the problem is still there after applying the patch:
{noformat}
hive> set system:java.io.tmpdir;
set system:java.io.tmpdir;
system:java.io.tmpdir=/var/folders/6d/bmvmcxh938q6htnxtyg9jk5r0000gn/T/
hive> SHOW TABLES;
...
hive> !ls ${system:java.io.tmpdir};
...
hive-default-187929306310164734.xml
hive-default-433053476043176173.xml
hive-default-3093481938548070336.xml
hive-default-159172276671008947.xml
...
hive> !rm ${system:java.io.tmpdir}/hive-default*;
hive> SHOW TABLES;
Failed with exception java.io.IOException:java.lang.RuntimeException:
java.io.FileNotFoundException:
/var/folders/6d/bmvmcxh938q6htnxtyg9jk5r0000gn/T/hive-default-187929306310164734.xml
(No such file or directory)
Time taken: 0.081 seconds
{noformat}
It's also worth pointing out that previously we created a single copy of
hive-default that was used by all HiveConf instances, but with this patch in
place we create a new hive-default file for each HiveConf instance. Roughly
speaking this means that we end up creating at least one new hive-default file
for each statement that is executed.
> 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.9.0, 0.8.1, 0.8.0
> Reporter: Chris McConnell
> Assignee: Chris McConnell
> Fix For: 0.10.0, 0.9.0, 0.8.1
>
> 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
