ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able
Date Thu, 24 Aug 2017 19:50:00 GMT


Hadoop QA commented on AMBARI-21806:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> Repository Entities Which Can't Be Removed Should Be Hide-able
> --------------------------------------------------------------
>                 Key: AMBARI-21806
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>    Affects Versions: 2.6.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.6.0
>         Attachments: AMBARI-21806.patch
> 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}}
> - {{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

View raw message