ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-16100) Upgrade catalog 220 in not idempotent again
Date Tue, 26 Apr 2016 15:10:13 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-16100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmytro Sen updated AMBARI-16100:
--------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Unit tests passed locally
Committed to trunk

> Upgrade catalog 220 in not idempotent again
> -------------------------------------------
>
>                 Key: AMBARI-16100
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16100
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-upgrade
>    Affects Versions: 2.4.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16100.patch
>
>
> UpgradeCatalog220#updateKerberosDescriptorArtifact 
> {code}
>             KerberosIdentityDescriptor hdfsIdentity = hdfsService.getIdentity("hdfs");
>             KerberosComponentDescriptor namenodeComponent = hdfsService.getComponent("NAMENODE");
>             hdfsIdentity.setName("hdfs");
>             hdfsService.removeIdentity("hdfs");
> {code}
> in case of second run on same database we will have here NPE, coz that descriptor was
already removed. Before using him, we need check that descriptor is present and is not null



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

Mime
View raw message