hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3709) Stop storing default ConfVars in temp file
Date Wed, 28 Nov 2012 08:20:59 GMT

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

Carl Steinbach commented on HIVE-3709:
--------------------------------------

Another option for fixing this problem is to give administrators the ability to specify the
location where the temporary file should be written (for setuid processes running on POSIX
systems the conventional location is somewhere under /var). For example we could add a configuration
property named hive.process.local.temporary.dir and have it default to ${user.home}/.hive/${process_id}.


                
> 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

Mime
View raw message