You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2016/04/29 23:46:13 UTC

[jira] [Commented] (HDFS-10349) StorageContainerManager fails to compile after merge of HDFS-10312 maxDataLength enforcement.

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

Arpit Agarwal commented on HDFS-10349:
--------------------------------------

+1 thank you Chris. My merge from trunk must have broken this. I am sorry about that.

> StorageContainerManager fails to compile after merge of HDFS-10312 maxDataLength enforcement.
> ---------------------------------------------------------------------------------------------
>
>                 Key: HDFS-10349
>                 URL: https://issues.apache.org/jira/browse/HDFS-10349
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-10349-HDFS-7240.001.patch
>
>
> HDFS-10312 introduced enforcement of a configurable maximum data length while deserializing large block reports.  This change broke compilation of {{StorageContainerManager}} on the HDFS-7240 feature branch, due to a constructor signature change in {{DatanodeProtocolServerSideTranslatorPB}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org