hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8585) Fix initialization circularity between UserGroupInformation and HadoopConfiguration
Date Thu, 12 Jul 2012 16:56:35 GMT

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

Aaron T. Myers commented on HADOOP-8585:

bq. Wouldn't it have been easier to just suppress the warning as a false alarm?

That would certainly work, but it doesn't seem much easier to me. I also don't see how the
method used by this patch could possibly cause any problems, as it changes the behavior back
to what it was before the recently-committed HDFS-3568, i.e. each invocation of newLoginContext
will create a new HadoopConfiguration object.
> Fix initialization circularity between UserGroupInformation and HadoopConfiguration
> -----------------------------------------------------------------------------------
>                 Key: HADOOP-8585
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8585
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.0.1-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>             Fix For: 2.0.1-alpha
>         Attachments: HDFS-3632.001.patch
> Fix findbugs warning about initialization circularity between UserGroupInformation and
> From the findbugs text:
> {code}
> Initialization circularity between org.apache.hadoop.security.UserGroupInformation and
> Bug type IC_INIT_CIRCULARITY (click for details)
> In class org.apache.hadoop.security.UserGroupInformation
> In class org.apache.hadoop.security.UserGroupInformation$HadoopConfiguration
> At UserGroupInformation.java:[lines 76-1395]
> {code}

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


View raw message