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 "Hudson (JIRA)" <ji...@apache.org> on 2018/04/24 20:45:37 UTC
[jira] [Commented] (HDFS-10349) Ozone: 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=16450523#comment-16450523 ]
Hudson commented on HDFS-10349:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-10349. Ozone: StorageContainerManager fails to compile after merge (cnauroth: rev 8264b61656b8195d3a3e641ad94f265efd81fa8f)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/ozone/storage/StorageContainerManager.java
> Ozone: 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
> Priority: Major
> Fix For: HDFS-7240
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org