You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hawq.apache.org by "Matt (JIRA)" <ji...@apache.org> on 2016/08/23 22:46:20 UTC

[jira] [Updated] (HAWQ-1013) Move HAWQ Ambari plugin to Apache HAWQ

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

Matt updated HAWQ-1013:
-----------------------
    Summary: Move HAWQ Ambari plugin to Apache HAWQ  (was: Add a utility to help users add HAWQ to Ambari)

> Move HAWQ Ambari plugin to Apache HAWQ
> --------------------------------------
>
>                 Key: HAWQ-1013
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1013
>             Project: Apache HAWQ
>          Issue Type: New Feature
>          Components: Ambari
>            Reporter: Matt
>            Assignee: Alexander Denissov
>              Labels: UX
>             Fix For: backlog
>
>
> To add HAWQ and PXF to Ambari, users have to follow certain manual steps. 
> These manual steps include:
> - Adding HAWQ and PXF metainfo.xml files (containing metadata about the service) under the stack to be installed.
> - Adding repositories, where HAWQ and PXF rpms reside so that Ambari can use it during installation. This requires updating repoinfo.xml under the stack HAWQ and PXF is being added to.
> - Adding repositories to an existing stack managed by Ambari requires adding the repositories using the Ambari REST endpoint.
> The above steps can be automated using a script to improve the user experience while installing HAWQ using Ambari.



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