hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5333) The libhdfs append API is not coded correctly
Date Sun, 01 Mar 2009 09:03:15 GMT

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

dhruba borthakur updated HADOOP-5333:
-------------------------------------

    Attachment: libhdfsAppend.patch

There should be a lock around getJniENV() to ensure that only one thread creates the JVM and
the other threads use the same JVM. I am using the hashtable lock to protect the creation
of the JVM.

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


Mime
View raw message