hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joydeep Sen Sarma (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-232) metastore.warehouse configuration should use inherited hadoop configuration
Date Thu, 15 Jan 2009 05:23:59 GMT

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

Joydeep Sen Sarma commented on HIVE-232:
----------------------------------------

hmm - i don't understand this. maybe we need to ping dhruba. fs object has to have scheme
auth - otherwise how does it know what file system to talk to (and the fs object has already
been instantiated - it's not either a DistributedFileSystem object or a LocalFileSystem based
object). 

Is this reproducible (with a populated fs.default.name)?

> metastore.warehouse configuration should use inherited hadoop configuration
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-232
>                 URL: https://issues.apache.org/jira/browse/HIVE-232
>             Project: Hadoop Hive
>          Issue Type: Bug
>            Reporter: Josh Ferguson
>         Attachments: hive-232.patch
>
>
> the hive.metastore.warehouse.dir configuration property in hive-*.xml needs to use the
protocol, host, and port when it is inherited from the fs.name property in hadoop-site.xml.
> When it doesn't and no protocol is found then a broad range of "Move" operations when
the source and target are both in the DFS will fail.
> Currently this can be worked around by prepending the protocol, host and port of the
hadoop nameserver into the value of the hive.metastore.warehouse.dir property.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message