You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2017/08/24 17:04:00 UTC

[jira] [Created] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able

Jonathan Hurley created AMBARI-21806:
----------------------------------------

             Summary: Repository Entities Which Can't Be Removed Should Be Hide-able
                 Key: AMBARI-21806
                 URL: https://issues.apache.org/jira/browse/AMBARI-21806
             Project: Ambari
          Issue Type: Task
    Affects Versions: 2.6.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             Fix For: 2.6.0


Many tables have begun referencing {{repo_version}} since a simple {{version}} string is no longer sufficient to properly identify a repository. However, we allow a {{RepsitoryVersionEntity}} to be removed if it is in the following states:

- {{INIT}}
- {{INSTALL_FAILED}}
- {{OUT_OF_SYNC}}

The issue with removing the entities is that this would also force us to remove things like upgrades, service component versions, etc. Here are some options:

# Allow repository versions in {{INIT}} and {{INSTALL_FAILED}} to be removed, but for other states we'd need to keep it in the DB for history and perhaps add a {{hidden}} column. This would keep the referential integrity.
# Allow the removal of repository versions, but warn that it will also remove things like upgrades. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)