Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <788688581.162261265752348113.JavaMail.jira@brutus.apache.org>
Date: Tue, 9 Feb 2010 21:52:28 +0000 (UTC)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-939) libhdfs test is broken
In-Reply-To: <847552291.14241265074338769.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eli Collins updated HDFS-939:
-----------------------------

    Status: Patch Available  (was: Open)

> libhdfs test is broken
> ----------------------
>
>                 Key: HDFS-939
>                 URL: https://issues.apache.org/jira/browse/HDFS-939
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: contrib/libhdfs
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hdfs-939-1.patch
>
>
> The libhdfs test currently does not run because hadoop.tmp.dir is specified as a relative path, and it looks like a side-effect of HDFS-873 was that relative paths get made absolute, so build/test/libhdfs gets turned into /test/libhdfs, which the NN can not create. Let's make the test generate conf files that use the appropriate directory (build/test/libhdfs) specified by fully qualified URIs. 
> Also, are relative paths in conf files supported? If not rather than fail we should detect this and print a warning.

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