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

Shivram Mani updated HAWQ-1045:
-------------------------------
    Description: 
This is a requirement from Ambari integration. Side by side installation 
scenario to do HAWQ upgrade and verification.
The following rpm names and packaging strategy was agreed upon during the 
meeting with HAWQ, HAWQ-Ambari team and [~rvs]

The pxf component rpms will be renamed to include the package version as part 
of the package name.
Example:
    o pxf-hdf_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-json_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-hbase_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-hive_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-service_3_0_1-3.0.1-1088.el6.noarch.rpm (dependency: 
apache-tomcat-7.0.62)

PXF virtual RPM by the name pxf will have a direct dependency on the individual 
PXF RPMS (pxf-hdfs,pxf-hive,pxf-hbase). Will also be responsible for creating 
the symlinks (/usr/lib/pxf and /etc/pxf/conf).
Example:
    o pxf-3.0.1.0-1088.el6.noarch.rpm
Dependencies: 
    o pxf-hdf_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-json_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-hbase_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-hive_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-service_3_0_1-3.0.1-1088.el6.noarch.rpm 

We will be removing the RPM dependancies on hive and hbase from pxf-hive and 
pxf-hbase respectively.
Create and update the necessary rpm spec files to produce the above mentioned 
rpms.

The rationale behind including the version in the pxf component rpm names is to 
allow both version of the rpms to be installed side by side to felicitate HAWQ 
upgrade. In the absence of the package name update, the package will always 
remove the artifacts created by the old package.

  was:
This is a requirement from Ambari integration. Side by side installation 
scenario to do HAWQ upgrade and verification.
The following rpm names and packaging strategy was agreed upon during the 
meeting with HAWQ, HAWQ-Ambari team and [~rvs]

The pxf component rpms will be renamed to include the package version as part 
of the package name.
Example:
    o pxf-hdf_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-json_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-hbase_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-hive_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-service_3_0_1-3.0.1-1088.el6.noarch.rpm (dependency: 
apache-tomcat-7.0.62)

- PXF virtual RPM by the name pxf will have a direct dependency on the 
individual PXF RPMS (pxf-hdfs,pxf-hive,pxf-hbase). Will also be responsible for 
creating the symlinks (/usr/lib/pxf and /etc/pxf/conf).
Example:
    o pxf-3.0.1.0-1088.el6.noarch.rpm
Dependencies: 
    o pxf-hdf_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-json_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-hbase_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-hive_3_0_1-3.0.1-1088.el6.noarch.rpm
    o pxf-service_3_0_1-3.0.1-1088.el6.noarch.rpm 

We will be removing the RPM dependancies on hive and hbase from pxf-hive and 
pxf-hbase respectively.
Create and update the necessary rpm spec files to produce the above mentioned 
rpms.

The rationale behind including the version in the pxf component rpm names is to 
allow both version of the rpms to be installed side by side to felicitate HAWQ 
upgrade. In the absence of the package name update, the package will always 
remove the artifacts created by the old package.


> Update PXF rpm to include virtual RPM
> -------------------------------------
>
>                 Key: HAWQ-1045
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1045
>             Project: Apache HAWQ
>          Issue Type: Task
>          Components: Build, PXF
>            Reporter: Goden Yao
>            Assignee: Shivram Mani
>             Fix For: 2.0.1.0-incubating
>
>
> This is a requirement from Ambari integration. Side by side installation 
> scenario to do HAWQ upgrade and verification.
> The following rpm names and packaging strategy was agreed upon during the 
> meeting with HAWQ, HAWQ-Ambari team and [~rvs]
> The pxf component rpms will be renamed to include the package version as part 
> of the package name.
> Example:
>     o pxf-hdf_3_0_1-3.0.1-1088.el6.noarch.rpm
>     o pxf-json_3_0_1-3.0.1-1088.el6.noarch.rpm
>     o pxf-hbase_3_0_1-3.0.1-1088.el6.noarch.rpm
>     o pxf-hive_3_0_1-3.0.1-1088.el6.noarch.rpm
>     o pxf-service_3_0_1-3.0.1-1088.el6.noarch.rpm (dependency: 
> apache-tomcat-7.0.62)
> PXF virtual RPM by the name pxf will have a direct dependency on the 
> individual PXF RPMS (pxf-hdfs,pxf-hive,pxf-hbase). Will also be responsible 
> for creating the symlinks (/usr/lib/pxf and /etc/pxf/conf).
> Example:
>     o pxf-3.0.1.0-1088.el6.noarch.rpm
> Dependencies: 
>     o pxf-hdf_3_0_1-3.0.1-1088.el6.noarch.rpm
>     o pxf-json_3_0_1-3.0.1-1088.el6.noarch.rpm
>     o pxf-hbase_3_0_1-3.0.1-1088.el6.noarch.rpm
>     o pxf-hive_3_0_1-3.0.1-1088.el6.noarch.rpm
>     o pxf-service_3_0_1-3.0.1-1088.el6.noarch.rpm 
> We will be removing the RPM dependancies on hive and hbase from pxf-hive and 
> pxf-hbase respectively.
> Create and update the necessary rpm spec files to produce the above mentioned 
> rpms.
> The rationale behind including the version in the pxf component rpm names is 
> to allow both version of the rpms to be installed side by side to felicitate 
> HAWQ upgrade. In the absence of the package name update, the package will 
> always remove the artifacts created by the old package.



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

Reply via email to