ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Thorpe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18050) Upgrade pre-req check code needs to be decoupled from CheckDescription class
Date Fri, 09 Sep 2016 16:50:22 GMT

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

Tim Thorpe commented on AMBARI-18050:
-------------------------------------

mvn clean test -Dtest=AbstractCheckDescriptorTest,UpgradeCheckOrderTest,CheckHelperTest
Ran 267 tests in 8.183s
Total run:1124
Total errors:0
Total failures:0


> Upgrade pre-req check code needs to be decoupled from CheckDescription class
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-18050
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18050
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>
> Each pre-req check must add an entry in the CheckDescription enum.  This obviously requires
a change to ambari-server java code.  This limits the ability for third party stacks and extensions
to provide their own pre-req checks.
> CheckDescription should be rewritten as a class and each pre-req check class should create
an instance of it.  This will allow stacks and extensions to include their own pre-req checks
in separate jar files without requiring changes to ambari-server java code.



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

Mime
View raw message