[ https://issues.apache.org/jira/browse/HAWQ-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435483#comment-15435483 ]
Vineet Goel commented on HAWQ-1013: ----------------------------------- RPM packaging is a build-time decision, separate from source code management. There are pros and cons to both. Separate RPM allows the flexibility of a quick install required on Ambari-server node only, where HAWQ binaries may not be necessary (depending on cluster size and topology). > 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 HAWQ Ambari plugin automates the above steps using a script. -- This message was sent by Atlassian JIRA (v6.3.4#6332)