hadoop-hive-dev mailing list archives

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

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

Prasad Chakka commented on HIVE-232:

The reference in DB.java will go away after removing old metastore code.

when input path is just simply '/user/hive/warehouse/dir1' then the FileSystem.get() call
doesn't know which the scheme/auth to use. It doesn't use the config  param fs.default.name
value. That is the reason why Josh/Jeremy were getting errors when 'hdfs://localhost:9000'
wasn't in the load inpath file name.

May be I could just set fromAuthority in local mode to be null and if the scheme is hdfs then
it to be what ever is given in the input URI or the fs.default.name's authority instead of
determining it from fs.getURI().getAuthority().

> 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.

View raw message