phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pedro Boado (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-4372) Distribution of Apache Phoenix 4.13 for CDH 5.11.2
Date Wed, 22 Nov 2017 01:04:50 GMT

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

Pedro Boado edited comment on PHOENIX-4372 at 11/22/17 1:03 AM:
----------------------------------------------------------------

{quote}What would be the next step, Pedro?{quote}
Next step would probably be pushing it to a new branch, run all IT and do a project build.
As part of the build process a file {{phoenix-parcel/target/APACHE-PHOENIX-*.parcel}} will
be generated.

Once we have this file, completing the release only needs running [https://github.com/cloudera/cm_ext/tree/master/make_manifest]
script  ( some additional notes [https://github.com/cloudera/cm_ext/wiki/The-parcel-repository-format]
) and publishing parcels + manifests to a webserver  ( let's say  https://phoenix.apache.org/parcels/4.13.1-cdh5.11.2/
). The script requires to run in a machine with python 2.7 or greater. It would also be great
having directory listing enabled for any directory under https://phoenix.apache.org/parcels/
.

This first release will have a hard dependency on CDH versions ( will only be installable
in cdh 5.11.2 ) . We may widen compatibility scopes to MAJOR.MINOR versions but that would
require removing all transitive embedded dependencies to hbase, hadoop etc etc from all of
Phoenix' uberjars ( Phoenix fat client jar is 100MB ). And I think we can do that in a second
parcel release.

Anyway, parcels have their own versioning - file name is {{APACHE-PHOENIX-4.13.1-cdh5.11.2-p0.0-rhel6.parcel}}
- where p0.0 is the parcel's release. Releasing a new version of the parcel removing all CDH
embedded dependencies  ( to improve compatibility across different CDH versions ) would be
a matter of releasing a new parcel increasing version to p0.1 or p1.0 or whatever. 




was (Author: pboado):
{quote}What would be the next step, Pedro?{quote}
Next step would probably be pushing it to a new branch, run all IT and do a project build.
As part of the build process a file {{phoenix-parcel/target/APACHE-PHOENIX-*.parcel}} will
be generated.

Once we have this file, completing the release only needs running [https://github.com/cloudera/cm_ext/tree/master/make_manifest]
script  ( some additional notes [https://github.com/cloudera/cm_ext/wiki/The-parcel-repository-format]
) and publishing parcels + manifests to a webserver  ( let's say  https://phoenix.apache.org/parcels/4.13.1-cdh5.11.2/
). The script requires to run in a machine with python 2.7 or greater. It would also be great
having directory listing enabled for any directory under https://phoenix.apache.org/parcels/
.

This first release will have a hard dependency on CDH versions ( will only be installable
in cdh 5.11.2 ) . We may widen compatibility scopes to MAJOR.MINOR versions but that would
require removing all transitive embedded dependencies to hbase, hadoop etc etc from all of
Phoenix' uberjars ( Phoenix fat client jar is 100MB ). 

Parcels have their own versioning - file name is {{APACHE-PHOENIX-4.13.1-cdh5.11.2-p0.0-rhel6.parcel}}
- where p0.0 is the parcel's release. Releasing a new version of the parcel removing all CDH
embedded dependencies  ( to improve compatibility across different CDH versions ) would be
a matter of releasing a new parcel. 



> Distribution of Apache Phoenix 4.13 for CDH 5.11.2
> --------------------------------------------------
>
>                 Key: PHOENIX-4372
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4372
>             Project: Phoenix
>          Issue Type: Task
>    Affects Versions: 4.13.0
>            Reporter: Pedro Boado
>            Assignee: Pedro Boado
>            Priority: Minor
>              Labels: cdh
>         Attachments: PHOENIX-4372-v2.patch, PHOENIX-4372-v3.patch, PHOENIX-4372-v4.patch,
PHOENIX-4372.patch
>
>
> Changes required on top of branch 4.13-HBase-1.2 for creating a parcel of Apache Phoenix
4.13.0 for CDH 5.11.2 . 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message