Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <142663763.1236632750422.JavaMail.jira@brutus>
Date: Mon, 9 Mar 2009 14:05:50 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5333) The libhdfs append API is not coded
 correctly
In-Reply-To: <1382775696.1235638865042.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680279#action_12680279 ] 

dhruba borthakur commented on HADOOP-5333:
------------------------------------------

Thanks a bunch Chris for reviewing this patch.

Only one JVM is needed. It would be nice to create the JVM during initialization rather than lazily in getJNIEnv(). But since libhdfs is a library and there are no "main" methods, can you suggest which "initialization" method might create the JVM?

I can create a different lock solely for this initialization (instead of using LOCK_HASH_TABLE).

> The libhdfs append API is not coded correctly
> ---------------------------------------------
>
>                 Key: HADOOP-5333
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5333
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: libhdfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>             Fix For: 0.19.2, 0.20.0, 0.21.0
>
>         Attachments: libhdfsAppend.patch, libhdfsAppend.patch
>
>
> The hdfsOpenFile() API does not handle the APPEND bit correctly.

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