ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Denissov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
Date Thu, 11 Aug 2016 19:19:20 GMT

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

Alexander Denissov commented on AMBARI-17285:
---------------------------------------------

Right. This means that without a fix users will only be able to install HAWQ if they choose
the default VDF, which is usually obsolete and refers to the older maintenance versions. A
user would have to choose between installing the most recent stack without HAWQ and installing
HAWQ with the older stack. This is not a choice we want the users to make, we would like them
to be able to install the latest stack with HAWQ right out of the box.

> Custom service repos in repoinfo.xml got overwritten by public VDFs
> -------------------------------------------------------------------
>
>                 Key: AMBARI-17285
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17285
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Alexander Denissov
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.4.0
>
>
> Ambari 2.4 introduced Version Definition Files that break the functionality of adding
a custom service repo, since custom services do not have an entry in the public VDF.
> In the case of HAWQ, the plugin is installed on Ambari host and it adds the new repo
information to the repoinfo.xml of all available stacks on the file system. Once Ambari cluster
creation wizard queries the latest repo info from the public URLs, it will get the info for
all stack repos, but not the custom ones. 
> So, the logic should be:
> 1. Use default repoinfo (from file system) as the base
> 2. Query public VDF, if available
> 3. For each entry in public VDF overwrite values in the default repoinfo
> 4. Entries in default repoinfo that do not have corresponding entries in VDF should stay
intact
> This way custom services can be added via file edit and the latest information can still
be retrieved and applied for the standard stack.



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

Mime
View raw message