You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2016/10/17 20:40:59 UTC
[jira] [Commented] (HADOOP-13543) [Umbrella] Analyse 2.8.0 and
3.0.0-alpha1 jdiff reports and fix any issues
[ https://issues.apache.org/jira/browse/HADOOP-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583392#comment-15583392 ]
Andrew Wang commented on HADOOP-13543:
--------------------------------------
Looks like we've lost steam on this issue. I generated a Java ACC report as part of the 3.0.0-alpha1 release, and I know at least I looked through Hadoop and HDFS, and Ray through YARN and MR.
In light of this, do we want to keep pushing on this JDiff work? I don't see it as a 3.0.0-beta1 blocker at least, since I can keep generating the JACC reports.
> [Umbrella] Analyse 2.8.0 and 3.0.0-alpha1 jdiff reports and fix any issues
> --------------------------------------------------------------------------
>
> Key: HADOOP-13543
> URL: https://issues.apache.org/jira/browse/HADOOP-13543
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
>
> Now that we have fixed JDiff report generation for 2.8.0 and above, we should analyse them.
> For the previous releases, I was applying the jdiff patches myself, and analysed them offline. It's better to track them here now that the reports are automatically getting generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org