You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2008/02/14 19:45:09 UTC

[jira] Updated: (HBASE-446) Fully qualified hbase.rootdir doesn't work

     [ https://issues.apache.org/jira/browse/HBASE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Kellerman updated HBASE-446:
--------------------------------

    Description: 
Jim was setting up cluster w/ new hbase.  Setting fully qualified hbase.rootdir was failing.  Complaint was that the filesystems didn't match -- i.e. the hdfs of the fully qualified hbase.rootdir didn't jibe w/ the default hadoop file:///.

Fix needs to be backported.

The problem was that because the hadoop config files were not found (because they are in a different directory and not on the classpath) then fs.get(conf) returns file:///


  was:
Jim was setting up cluster w/ new hbase.  Setting fully qualified hbase.rootdir was failing.  Complaint was that the filesystems didn't match -- i.e. the hdfs of the fully qualified hbase.rootdir didn't jibe w/ the default hadoop file:///.

Fix needs to be backported.

        Summary: Fully qualified hbase.rootdir doesn't work  (was: Fully qualified hbase.rootdir ain't working)

> Fully qualified hbase.rootdir doesn't work
> ------------------------------------------
>
>                 Key: HBASE-446
>                 URL: https://issues.apache.org/jira/browse/HBASE-446
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.1.0, 0.2.0
>            Reporter: stack
>            Priority: Blocker
>         Attachments: patch.txt
>
>
> Jim was setting up cluster w/ new hbase.  Setting fully qualified hbase.rootdir was failing.  Complaint was that the filesystems didn't match -- i.e. the hdfs of the fully qualified hbase.rootdir didn't jibe w/ the default hadoop file:///.
> Fix needs to be backported.
> The problem was that because the hadoop config files were not found (because they are in a different directory and not on the classpath) then fs.get(conf) returns file:///

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