[
https://issues.apache.org/jira/browse/HIVE-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505455#comment-13505455
]
Chris McConnell commented on HIVE-3709:
---------------------------------------
I was also looking into this with 3596, I was able to fix utilizing a location
similar to the suggestion Carl made above, however I think that pushes the
problem to another location, rather than addressing the actual issue. I like
where Kevin is going with this fix, I had thought about the possibility of
checking the confVarURL in the copy constructor, removing and re-creating if it
did not exist, but even that would not be perfect depending upon timing.
> Stop storing default ConfVars in temp file
> ------------------------------------------
>
> Key: HIVE-3709
> URL: https://issues.apache.org/jira/browse/HIVE-3709
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.10.0
> Reporter: Kevin Wilfong
> Assignee: Kevin Wilfong
> Attachments: HIVE-3709.1.patch.txt, HIVE-3709.2.patch.txt,
> HIVE-3709.3.patch.txt
>
>
> To work around issues with Hadoop's Configuration object, specifically it's
> addResource(InputStream), default configurations are written to a temp file
> (I think HIVE-2362 introduced this).
> This, however, introduces the problem that once that file is deleted from
> /tmp the client crashes. This is particularly problematic for long running
> services like the metastore server.
> Writing a custom InputStream to deal with the problems in the Configuration
> object should provide a work around, which does not introduce a time bomb
> into Hive.
--
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
