[
https://issues.apache.org/jira/browse/HIVE-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497681#comment-13497681
]
Phabricator commented on HIVE-3431:
-----------------------------------
navis has commented on the revision "HIVE-3431 [jira] Resources on non-local
file system should be downloaded to temporary directory sometimes".
hive-default.xml.template will be updated. I always forget that.
INLINE COMMENTS
ql/src/java/org/apache/hadoop/hive/ql/session/SessionState.java:605
DOWNLOADED_RESOURCES_DIR has default value and I think it's meaningless to set
the value as null. But.. I'll check it.
ql/src/java/org/apache/hadoop/hive/ql/session/SessionState.java:609 Agree on
your thoughts. It seemed possible to specify 'temporary' for implying
$WORKING_HOME/temporary.
This would be a good chance to making a convention for hive internal magic
words something like "@hive_<value>". Have some idea?
REVISION DETAIL
https://reviews.facebook.net/D5199
To: JIRA, navis
Cc: mgrover
> Resources on non-local file system should be downloaded to temporary
> directory sometimes
> ----------------------------------------------------------------------------------------
>
> Key: HIVE-3431
> URL: https://issues.apache.org/jira/browse/HIVE-3431
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.10.0
> Reporter: Navis
> Assignee: Navis
> Priority: Trivial
> Attachments: HIVE-3431.1.patch.txt
>
>
> "add resource <remote-uri>" command downloads the resource file to location
> specified by conf "hive.downloaded.resources.dir" in local file system. But
> when the command above is executed concurrently to hive-server for same file,
> some client fails by VM crash, which is caused by overwritten file by other
> requests.
> So there should be a configuration to provide per request location for add
> resource command, something like "set
> hiveconf:hive.downloaded.resources.dir=temporary"
--
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
