[
https://issues.apache.org/jira/browse/PHOENIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258554#comment-16258554
]
Pedro Boado edited comment on PHOENIX-4372 at 11/19/17 6:20 PM:
----------------------------------------------------------------
{{SystemTablePermissionsIT}} runs on its own, but {{IndexScrutinyToolIT}}
fails.
Yep, we are almost there.
The ideal release I think it would be sources linked from Phoenix website as
.tar.gz + maven artifacts uploaded to maven central (this would REALLY help) +
binaries in a parcel repository ( it's the automated installation way for
Cloudera Manager ) . I think this way of releasing would increase popularity of
Apache Phoenix among CDH adopters. Sysadmins would only have to add an URL to
their Cloudera Managers, press a couple of Next, Next buttons and that's it!
Phoenix installed- .
A repository is just a folder in a http server containing {{.parcel}} files -
which are .tar files following a certain format - plus a manifest.json that
lists all parcels in the repository (plus its hashes) . There is a python
script somewhere in Cloudera's site to generate this manifest.json file for a
certain folder. I'll try to find it. An example of a CDH repo would be
[http://archive.cloudera.com/cloudera-labs/phoenix/parcels/1.2.0/] . Each
.parcel version is for a different Linux distribution. For now I have only
added code in the project for generating files for RHEL6 ( reverse-engineered
from cloudera labs repository) but I aim to add support for RHEL7 and then for
other versions of Linux ( here I'd need help testing them )
Regarding branching, there is no need for adding HBase version ( as it's
coupled to CDH version ) . I would go for branch naming {{4.x-cdh5.11.2}} and
releases {{4.13.1-cdh5.11.2}}
I'll send the pull request as soon as these two tests are running and/or have
decided what to do with them.
was (Author: pboado):
{{SystemTablePermissionsIT}} runs on its own, but {{IndexScrutinyToolIT}}
fails.
Yep, we are almost there.
The ideal release I think it would be sources linked from Phoenix website as
.tar.gz + maven artifacts uploaded to maven central (this would REALLY help) +
binaries in a parcel repository ( it's the automated installation way for
Cloudera Manager ) . I think this way of releasing would increase popularity of
Apache Phoenix among CDH adopters. Sysadmins would only have to add an URL to
their Cloudera Managers, press a couple of Next, Next buttons and that's it!
Phoenix installed- .
A repository is just a folder in a http server containing {{.parcel}} files -
which are .tar files following a certain format - plus a manifest.json that
lists all parcels in the repository (plus its hashes) . There is a python
script somewhere in Cloudera's site to generate this manifest.json file for a
certain folder. I'll try to find it. An example of a CDH repo would be
[http://archive.cloudera.com/cloudera-labs/phoenix/parcels/1.2.0/] . Each
.parcel version is for a different Linux distribution. For now I have only
added code in the project for generating files for RHEL6 ( reverse-engineered
from cloudera labs repository) but I aim to add support for RHEL7 and then for
other versions of Linux ( here I'd need help testing them )
Regarding branching, there is no need for adding HBase version ( as it's
coupled to CDH version ) . I would go for branch naming {{4.x-cdh5.11.2}} and
releases {{4.13.1-cdh5.11.2}}
I'll send the pull request as soon as these two tests are running and/or
decided what to do with them.
> 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.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)
