Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 5 Jan 2012 21:42:39 +0000 (UTC)
From: "Eli Collins (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <10975902.11680.1325799759342.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <541078820.37868.1324520970654.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7937) Forward port SequenceFile#syncFs
 and friends from Hadoop 1.x
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eli Collins commented on HADOOP-7937:
-------------------------------------

+1  (assuming the javac warning is unrelated, should be) 

Looking at the other HDFS changes, agree that we probably don't need to forward port these.  Given that they're just used via DFSClient, perhaps we should restrict the visibility in branch-1 to be more limited or javadoc that they won't be compatible?
                
> Forward port SequenceFile#syncFs and friends from Hadoop 1.x
> ------------------------------------------------------------
>
>                 Key: HADOOP-7937
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7937
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: io
>    Affects Versions: 0.22.0, 0.23.1
>            Reporter: Eli Collins
>            Assignee: Tom White
>              Labels: bigtop
>         Attachments: HADOOP-7937.patch
>
>
> HDFS-200 added a new public API SequenceFile#syncFs, we need to forward port this for compatibility. Looks like it might have introduced other APIs that need forward porting as well (eg LocaltedBlocks#setFileLength, and DataNode#getBlockInfo).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira