[jira] [Commented] (HAWQ-1421) Improve PXF rpm package name format and dependencies

2017-03-29 Thread Radar Lei (JIRA) 

[ 
https://issues.apache.org/jira/browse/HAWQ-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948361#comment-15948361
 ] 

Radar Lei commented on HAWQ-1421:
-

Thanks [~shivram], most changes looks great!

 But for pxf dependencies, I failed to get pxf rpm installed with HDP 
installed. Please verify PXF can work with these hadoop distributions. 

rpm -ivh pxf-hdfs-3.2.1.0-1.el6.noarch.rpm
error: Failed dependencies:
pxf-service >= 3.2.1.0 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch
hadoop-mapreduce >= 2.7.1 is needed by pxf-hdfs-0:3.2.1.0-1.el6.noarch

rpm -qa |grep hdfs
hadoop_2_5_0_0_1245-hdfs-2.7.3.2.5.0.0-1245.el6.x86_64
hadoop_2_5_0_0_1245-hdfs-secondarynamenode-2.7.3.2.5.0.0-1245.el6.x86_64
ranger-hdfs-plugin-0.6.0.2.5.0.0-1245.el6.noarch
hadoop_2_5_0_0_1245-hdfs-namenode-2.7.3.2.5.0.0-1245.el6.x86_64
ranger_2_5_0_0_1245-hdfs-plugin-0.6.0.2.5.0.0-1245.el6.x86_64
hadoop_2_5_0_0_1245-hdfs-datanode-2.7.3.2.5.0.0-1245.el6.x86_64

Another thought is user might using binary hadoop without rpm installs, will 
PXF works with this situation?

> Improve PXF rpm package name format and dependencies
> 
>
> Key: HAWQ-1421
> URL: https://issues.apache.org/jira/browse/HAWQ-1421
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build, PXF
>Reporter: Radar Lei
>Assignee: Shivram Mani
> Fix For: 2.2.0.0-incubating
>
>
> If we build pxf rpm package by 'make rpm', we will get below pxf packages:
> {quote}
>   apache-tomcat-7.0.62-el6.noarch.rpm
>   pxf-3.2.1.0-root.el6.noarch.rpm
>   pxf-hbase_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hive_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-jdbc_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-json_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-service_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> {quote}
> These rpm packages have dependencies on Apache Hadoop components only, some 
> other Hadoop distributes can't satisfy it. E.g. :
> {quote}
> rpm -ivh pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> error: Failed dependencies:
>   pxf-service_3_2_1_0 >= 3.2.1.0 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop >= 2.7.1 is needed by pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop-mapreduce >= 2.7.1 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
> {quote}
> We'd better make the rpm package name format and dependencies better. 
>   1. Remove the version string like '3_2_1_0'.
>   2. Remove the user name from the build environment.
>   3. Consider do we need to include the apache-tomcat rpm package into HAWQ 
> rpm release tarball.
>   4. Improve the hard code 'el6' string. (This might be optinal)
>   5. Improve the dependencies, including the dependencies between these pxf 
> rpm packages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-hawq issue #1203: Enable build of Ranger plugin open source RPM

2017-03-29 Thread radarwave 
Github user radarwave commented on the issue:

https://github.com/apache/incubator-hawq/pull/1203
  
Now the rpm name is: hawq-ranger-plugin-2.2.0.0-1.el7.centos.noarch.rpm

How about we remove the string 'centos' since there is already a 'el7' 
string there?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq issue #1203: Enable build of Ranger plugin open source RPM

2017-03-29 Thread radarwave 
Github user radarwave commented on the issue:

https://github.com/apache/incubator-hawq/pull/1203
  
Now hawq ranger plugin rpm is in different directory, we should update the  
tarball script 'contrib/hawq-package/make_rpm_tarball.sh' with the new copy 
directory:

-cp 
${SRC_TOP_DIR}/ranger-plugin/target/rpm/hawq-ranger-plugin_*/RPMS/noarch/hawq-ranger-plugin*.rpm
 ${RPM_PKG_DIR}/
+cp 
${SRC_TOP_DIR}/ranger-plugin/target/rpm/hawq-ranger-plugin*/RPMS/noarch/hawq-ranger-plugin*.rpm
 ${RPM_PKG_DIR}/


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #1208: HAWQ-1421. PXF rpm updates to make it oss...

2017-03-29 Thread shivzone 
GitHub user shivzone opened a pull request:

https://github.com/apache/incubator-hawq/pull/1208

HAWQ-1421. PXF rpm updates to make it oss friendly



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/incubator-hawq HAWQ-1421

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-hawq/pull/1208.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1208


commit e0102a821204c72c8f4cfe99562b8d27fb4cf967
Author: shivzone 
Date:   2017-03-30T01:15:37Z

HAWQ-1421. PXF rpm updates to make it oss friendly




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Comment Edited] (HAWQ-1421) Improve PXF rpm package name format and dependencies

2017-03-29 Thread Shivram Mani (JIRA) 

[ 
https://issues.apache.org/jira/browse/HAWQ-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948210#comment-15948210
 ] 

Shivram Mani edited comment on HAWQ-1421 at 3/30/17 1:18 AM:
-

The following is the output on running make rpm for PXF
{code}
BUILD SUCCESSFUL
Total time: 48.714 secs
shivram:pxf shivram$ vim build/distributions/pxf-
pxf-3.2.1.0-shivram.el6.noarch.rpm  
pxf-hbase-3.2.1.0-shivram.el6.noarch.rpm
pxf-hdfs-3.2.1.0-shivram.el6.noarch.rpm 
pxf-hive-3.2.1.0-shivram.el6.noarch.rpm 
pxf-jdbc-3.2.1.0-shivram.el6.noarch.rpm 
pxf-json-3.2.1.0-shivram.el6.noarch.rpm 
pxf-service-3.2.1.0-shivram.el6.noarch.rpm
{code}
When the build number is set:
{code}
export BUILD_NUMBER=1
BUILD SUCCESSFUL
Total time: 43.94 secs
shivram:pxf shivram$ vim build/distributions/pxf-
pxf-3.2.1.0-1.el6.noarch.rpm  pxf-hbase-3.2.1.0-1.el6.noarch.rpm
pxf-hdfs-3.2.1.0-1.el6.noarch.rpm pxf-hive-3.2.1.0-1.el6.noarch.rpm 
pxf-jdbc-3.2.1.0-1.el6.noarch.rpm pxf-json-3.2.1.0-1.el6.noarch.rpm 
pxf-service-3.2.1.0-1.el6.noarch.rpm
{code}


was (Author: shivram):
The following is the output on running make rpm for PXF
```
BUILD SUCCESSFUL
Total time: 48.714 secs
shivram:pxf shivram$ vim build/distributions/pxf-
pxf-3.2.1.0-shivram.el6.noarch.rpm  
pxf-hbase-3.2.1.0-shivram.el6.noarch.rpm
pxf-hdfs-3.2.1.0-shivram.el6.noarch.rpm 
pxf-hive-3.2.1.0-shivram.el6.noarch.rpm 
pxf-jdbc-3.2.1.0-shivram.el6.noarch.rpm 
pxf-json-3.2.1.0-shivram.el6.noarch.rpm 
pxf-service-3.2.1.0-shivram.el6.noarch.rpm
```
When the build number is set:
```
export BUILD_NUMBER=1
BUILD SUCCESSFUL
Total time: 43.94 secs
shivram:pxf shivram$ vim build/distributions/pxf-
pxf-3.2.1.0-1.el6.noarch.rpm  pxf-hbase-3.2.1.0-1.el6.noarch.rpm
pxf-hdfs-3.2.1.0-1.el6.noarch.rpm pxf-hive-3.2.1.0-1.el6.noarch.rpm 
pxf-jdbc-3.2.1.0-1.el6.noarch.rpm pxf-json-3.2.1.0-1.el6.noarch.rpm 
pxf-service-3.2.1.0-1.el6.noarch.rpm
```

> Improve PXF rpm package name format and dependencies
> 
>
> Key: HAWQ-1421
> URL: https://issues.apache.org/jira/browse/HAWQ-1421
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build, PXF
>Reporter: Radar Lei
>Assignee: Shivram Mani
> Fix For: 2.2.0.0-incubating
>
>
> If we build pxf rpm package by 'make rpm', we will get below pxf packages:
> {quote}
>   apache-tomcat-7.0.62-el6.noarch.rpm
>   pxf-3.2.1.0-root.el6.noarch.rpm
>   pxf-hbase_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hive_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-jdbc_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-json_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-service_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> {quote}
> These rpm packages have dependencies on Apache Hadoop components only, some 
> other Hadoop distributes can't satisfy it. E.g. :
> {quote}
> rpm -ivh pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> error: Failed dependencies:
>   pxf-service_3_2_1_0 >= 3.2.1.0 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop >= 2.7.1 is needed by pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop-mapreduce >= 2.7.1 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
> {quote}
> We'd better make the rpm package name format and dependencies better. 
>   1. Remove the version string like '3_2_1_0'.
>   2. Remove the user name from the build environment.
>   3. Consider do we need to include the apache-tomcat rpm package into HAWQ 
> rpm release tarball.
>   4. Improve the hard code 'el6' string. (This might be optinal)
>   5. Improve the dependencies, including the dependencies between these pxf 
> rpm packages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (HAWQ-1421) Improve PXF rpm package name format and dependencies

2017-03-29 Thread Shivram Mani (JIRA) 

[ 
https://issues.apache.org/jira/browse/HAWQ-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948210#comment-15948210
 ] 

Shivram Mani commented on HAWQ-1421:


The following is the output on running make rpm for PXF
```
BUILD SUCCESSFUL
Total time: 48.714 secs
shivram:pxf shivram$ vim build/distributions/pxf-
pxf-3.2.1.0-shivram.el6.noarch.rpm  
pxf-hbase-3.2.1.0-shivram.el6.noarch.rpm
pxf-hdfs-3.2.1.0-shivram.el6.noarch.rpm 
pxf-hive-3.2.1.0-shivram.el6.noarch.rpm 
pxf-jdbc-3.2.1.0-shivram.el6.noarch.rpm 
pxf-json-3.2.1.0-shivram.el6.noarch.rpm 
pxf-service-3.2.1.0-shivram.el6.noarch.rpm
```
When the build number is set:
```
export BUILD_NUMBER=1
BUILD SUCCESSFUL
Total time: 43.94 secs
shivram:pxf shivram$ vim build/distributions/pxf-
pxf-3.2.1.0-1.el6.noarch.rpm  pxf-hbase-3.2.1.0-1.el6.noarch.rpm
pxf-hdfs-3.2.1.0-1.el6.noarch.rpm pxf-hive-3.2.1.0-1.el6.noarch.rpm 
pxf-jdbc-3.2.1.0-1.el6.noarch.rpm pxf-json-3.2.1.0-1.el6.noarch.rpm 
pxf-service-3.2.1.0-1.el6.noarch.rpm
```

> Improve PXF rpm package name format and dependencies
> 
>
> Key: HAWQ-1421
> URL: https://issues.apache.org/jira/browse/HAWQ-1421
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build, PXF
>Reporter: Radar Lei
>Assignee: Shivram Mani
> Fix For: 2.2.0.0-incubating
>
>
> If we build pxf rpm package by 'make rpm', we will get below pxf packages:
> {quote}
>   apache-tomcat-7.0.62-el6.noarch.rpm
>   pxf-3.2.1.0-root.el6.noarch.rpm
>   pxf-hbase_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hive_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-jdbc_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-json_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-service_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> {quote}
> These rpm packages have dependencies on Apache Hadoop components only, some 
> other Hadoop distributes can't satisfy it. E.g. :
> {quote}
> rpm -ivh pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> error: Failed dependencies:
>   pxf-service_3_2_1_0 >= 3.2.1.0 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop >= 2.7.1 is needed by pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop-mapreduce >= 2.7.1 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
> {quote}
> We'd better make the rpm package name format and dependencies better. 
>   1. Remove the version string like '3_2_1_0'.
>   2. Remove the user name from the build environment.
>   3. Consider do we need to include the apache-tomcat rpm package into HAWQ 
> rpm release tarball.
>   4. Improve the hard code 'el6' string. (This might be optinal)
>   5. Improve the dependencies, including the dependencies between these pxf 
> rpm packages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (HAWQ-1421) Improve PXF rpm package name format and dependencies

2017-03-29 Thread Shivram Mani (JIRA) 

[ 
https://issues.apache.org/jira/browse/HAWQ-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948176#comment-15948176
 ] 

Shivram Mani commented on HAWQ-1421:


[~rlei] this is good feedback.
We can remove the version information from the rpm name.

With regards to the username, we will resort to using systems user.name only if 
the BUILD_NUMBER variable isn't set. Ideally the BUILD_NUMBER needs to be set. 
As a default i think it is fine if we stick to the username, otherwise we will 
have to default to a hardcoded value of 1 which isn't good.

We do need to include the apache tomcat rpm as this is not publicly available. 
tomcat is only distributed via source

I don't think we need to change any pxf rpm dependancies. Having dependancy on 
hadoop rpms works with all well known hadoop distributions

> Improve PXF rpm package name format and dependencies
> 
>
> Key: HAWQ-1421
> URL: https://issues.apache.org/jira/browse/HAWQ-1421
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build, PXF
>Reporter: Radar Lei
>Assignee: Shivram Mani
> Fix For: 2.2.0.0-incubating
>
>
> If we build pxf rpm package by 'make rpm', we will get below pxf packages:
> {quote}
>   apache-tomcat-7.0.62-el6.noarch.rpm
>   pxf-3.2.1.0-root.el6.noarch.rpm
>   pxf-hbase_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hive_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-jdbc_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-json_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-service_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> {quote}
> These rpm packages have dependencies on Apache Hadoop components only, some 
> other Hadoop distributes can't satisfy it. E.g. :
> {quote}
> rpm -ivh pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> error: Failed dependencies:
>   pxf-service_3_2_1_0 >= 3.2.1.0 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop >= 2.7.1 is needed by pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop-mapreduce >= 2.7.1 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
> {quote}
> We'd better make the rpm package name format and dependencies better. 
>   1. Remove the version string like '3_2_1_0'.
>   2. Remove the user name from the build environment.
>   3. Consider do we need to include the apache-tomcat rpm package into HAWQ 
> rpm release tarball.
>   4. Improve the hard code 'el6' string. (This might be optinal)
>   5. Improve the dependencies, including the dependencies between these pxf 
> rpm packages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (HAWQ-1421) Improve PXF rpm package name format and dependencies

2017-03-29 Thread Shivram Mani (JIRA) 

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

Shivram Mani reassigned HAWQ-1421:
--

Assignee: Shivram Mani  (was: Vineet Goel)

> Improve PXF rpm package name format and dependencies
> 
>
> Key: HAWQ-1421
> URL: https://issues.apache.org/jira/browse/HAWQ-1421
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build, PXF
>Reporter: Radar Lei
>Assignee: Shivram Mani
> Fix For: 2.2.0.0-incubating
>
>
> If we build pxf rpm package by 'make rpm', we will get below pxf packages:
> {quote}
>   apache-tomcat-7.0.62-el6.noarch.rpm
>   pxf-3.2.1.0-root.el6.noarch.rpm
>   pxf-hbase_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hive_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-jdbc_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-json_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-service_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> {quote}
> These rpm packages have dependencies on Apache Hadoop components only, some 
> other Hadoop distributes can't satisfy it. E.g. :
> {quote}
> rpm -ivh pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> error: Failed dependencies:
>   pxf-service_3_2_1_0 >= 3.2.1.0 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop >= 2.7.1 is needed by pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop-mapreduce >= 2.7.1 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
> {quote}
> We'd better make the rpm package name format and dependencies better. 
>   1. Remove the version string like '3_2_1_0'.
>   2. Remove the user name from the build environment.
>   3. Consider do we need to include the apache-tomcat rpm package into HAWQ 
> rpm release tarball.
>   4. Improve the hard code 'el6' string. (This might be optinal)
>   5. Improve the dependencies, including the dependencies between these pxf 
> rpm packages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (HAWQ-1421) Improve PXF rpm package name format and dependencies

2017-03-29 Thread Oleksandr Diachenko (JIRA) 

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

Oleksandr Diachenko updated HAWQ-1421:
--
Component/s: PXF

> Improve PXF rpm package name format and dependencies
> 
>
> Key: HAWQ-1421
> URL: https://issues.apache.org/jira/browse/HAWQ-1421
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build, PXF
>Reporter: Radar Lei
>Assignee: Vineet Goel
> Fix For: 2.2.0.0-incubating
>
>
> If we build pxf rpm package by 'make rpm', we will get below pxf packages:
> {quote}
>   apache-tomcat-7.0.62-el6.noarch.rpm
>   pxf-3.2.1.0-root.el6.noarch.rpm
>   pxf-hbase_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hive_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-jdbc_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-json_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-service_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> {quote}
> These rpm packages have dependencies on Apache Hadoop components only, some 
> other Hadoop distributes can't satisfy it. E.g. :
> {quote}
> rpm -ivh pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> error: Failed dependencies:
>   pxf-service_3_2_1_0 >= 3.2.1.0 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop >= 2.7.1 is needed by pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop-mapreduce >= 2.7.1 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
> {quote}
> We'd better make the rpm package name format and dependencies better. 
>   1. Remove the version string like '3_2_1_0'.
>   2. Remove the user name from the build environment.
>   3. Consider do we need to include the apache-tomcat rpm package into HAWQ 
> rpm release tarball.
>   4. Improve the hard code 'el6' string. (This might be optinal)
>   5. Improve the dependencies, including the dependencies between these pxf 
> rpm packages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-hawq issue #1203: Enable build of Ranger plugin open source RPM

2017-03-29 Thread ljainpivotalio 
Github user ljainpivotalio commented on the issue:

https://github.com/apache/incubator-hawq/pull/1203
  
@radarwave The open source build can override these values using maven 
command line:

BUILD_OPTS="-Drelease.version=bin -Dbuild.suffix= 
-Dhawq.dep.name=apache-hawq  -Ddestination.dir=/usr/local/apache-hawq"


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #1203: Enable build of Ranger plugin open source...

2017-03-29 Thread radarwave 
Github user radarwave commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1203#discussion_r108702120
  
--- Diff: ranger-plugin/pom.xml ---
@@ -38,6 +38,9 @@
 1
 9.1-901-1.jdbc4
 UTF-8
+_${hawq.name.version}
+hawq_${hawq.name.version}
+
/usr/local/hawq${build.suffix}/ranger
--- End diff --

Apache HAWQ will default get installed into /usr/local/apache-hawq.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (HAWQ-1421) Improve PXF rpm package name format and dependencies

2017-03-29 Thread Radar Lei (JIRA) 

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

Radar Lei reassigned HAWQ-1421:
---

Assignee: Vineet Goel  (was: Ed Espino)

> Improve PXF rpm package name format and dependencies
> 
>
> Key: HAWQ-1421
> URL: https://issues.apache.org/jira/browse/HAWQ-1421
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build
>Reporter: Radar Lei
>Assignee: Vineet Goel
> Fix For: 2.2.0.0-incubating
>
>
> If we build pxf rpm package by 'make rpm', we will get below pxf packages:
> {quote}
>   apache-tomcat-7.0.62-el6.noarch.rpm
>   pxf-3.2.1.0-root.el6.noarch.rpm
>   pxf-hbase_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-hive_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-jdbc_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-json_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
>   pxf-service_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> {quote}
> These rpm packages have dependencies on Apache Hadoop components only, some 
> other Hadoop distributes can't satisfy it. E.g. :
> {quote}
> rpm -ivh pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
> error: Failed dependencies:
>   pxf-service_3_2_1_0 >= 3.2.1.0 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop >= 2.7.1 is needed by pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
>   hadoop-mapreduce >= 2.7.1 is needed by 
> pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
> {quote}
> We'd better make the rpm package name format and dependencies better. 
>   1. Remove the version string like '3_2_1_0'.
>   2. Remove the user name from the build environment.
>   3. Consider do we need to include the apache-tomcat rpm package into HAWQ 
> rpm release tarball.
>   4. Improve the hard code 'el6' string. (This might be optinal)
>   5. Improve the dependencies, including the dependencies between these pxf 
> rpm packages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HAWQ-1421) Improve PXF rpm package name format and dependencies

2017-03-29 Thread Radar Lei (JIRA) 
Radar Lei created HAWQ-1421:
---

 Summary: Improve PXF rpm package name format and dependencies
 Key: HAWQ-1421
 URL: https://issues.apache.org/jira/browse/HAWQ-1421
 Project: Apache HAWQ
  Issue Type: Improvement
  Components: Build
Reporter: Radar Lei
Assignee: Ed Espino
 Fix For: 2.2.0.0-incubating


If we build pxf rpm package by 'make rpm', we will get below pxf packages:
{quote}
  apache-tomcat-7.0.62-el6.noarch.rpm
  pxf-3.2.1.0-root.el6.noarch.rpm
  pxf-hbase_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
  pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
  pxf-hive_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
  pxf-jdbc_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
  pxf-json_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
  pxf-service_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
{quote}

These rpm packages have dependencies on Apache Hadoop components only, some 
other Hadoop distributes can't satisfy it. E.g. :
{quote}
rpm -ivh pxf-hdfs_3_2_1_0-3.2.1.0-root.el6.noarch.rpm
error: Failed dependencies:
pxf-service_3_2_1_0 >= 3.2.1.0 is needed by 
pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
hadoop >= 2.7.1 is needed by pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
hadoop-mapreduce >= 2.7.1 is needed by 
pxf-hdfs_3_2_1_0-0:3.2.1.0-root.el6.noarch
{quote}

We'd better make the rpm package name format and dependencies better. 
  1. Remove the version string like '3_2_1_0'.
  2. Remove the user name from the build environment.
  3. Consider do we need to include the apache-tomcat rpm package into HAWQ rpm 
release tarball.
  4. Improve the hard code 'el6' string. (This might be optinal)
  5. Improve the dependencies, including the dependencies between these pxf rpm 
packages.





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (HAWQ-1391) s390x support for HWCRC32c

2017-03-29 Thread Namrata Bhave (JIRA) 

[ 
https://issues.apache.org/jira/browse/HAWQ-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947007#comment-15947007
 ] 

Namrata Bhave commented on HAWQ-1391:
-

I am working on building and testing HAWQ on s390x platform.
I am facing below error while executing make unittest-check in access/external:

[ RUN ] test__GPHD_HA_load_nodes__UnknownNameservice
[  OK ] test__GPHD_HA_load_nodes__UnknownNameservice
[ RUN ] test__GPHD_HA_load_nodes__OneNN
No entries for symbol hdfsFreeNamenodeInformation.
ERROR: ha_config_mock.c:38 - Could not get value to mock 
function hdfsFreeNamenodeInformation
Previously returned mock value was declared at 
ha_config_test.c:93
[  FAILED ] test__GPHD_HA_load_nodes__OneNN
[ RUN ] test__GPHD_HA_load_nodes__RpcDelimMissing
No entries for symbol hdfsFreeNamenodeInformation.
ERROR: ha_config_mock.c:38 - Could not get value to mock 
function hdfsFreeNamenodeInformation
Previously returned mock value was declared at 
ha_config_test.c:127
[  FAILED ] test__GPHD_HA_load_nodes__RpcDelimMissing
[ RUN ] test__GPHD_HA_load_nodes__PxfServicePortIsAssigned
port_to_str() has remaining non-returned values.
  Remaining item(s) declared at...
ha_config_test.c:163
ha_config_test.c:168
port_to_str() has remaining non-assigned out-values.
  Remaining item(s) declared at...
port:0
port_to_str.port parameter still has values that haven't been 
checked.
  Remaining item(s) declared at...
ha_config_test.c:164
ha_config_test.c:169
new_port parameter still has values that haven't been checked.
  Remaining item(s) declared at...
ha_config_test.c:165
ha_config_test.c:170
[  FAILED ] test__GPHD_HA_load_nodes__PxfServicePortIsAssigned
[ RUN ] test__GPHD_HA_load_nodes__HostMissing
port_to_str() has remaining non-returned values.
  Remaining item(s) declared at...
ha_config_test.c:197
ha_config_test.c:202
port_to_str() has remaining non-assigned out-values.
  Remaining item(s) declared at...
port:0
port_to_str.port parameter still has values that haven't been 
checked.
  Remaining item(s) declared at...
ha_config_test.c:198
ha_config_test.c:203
new_port parameter still has values that haven't been checked.
  Remaining item(s) declared at...
ha_config_test.c:199
ha_config_test.c:204
[  FAILED ] test__GPHD_HA_load_nodes__HostMissing
[ RUN ] test__GPHD_HA_load_nodes__PortMissing
port_to_str() has remaining non-returned values.
  Remaining item(s) declared at...
ha_config_test.c:238
ha_config_test.c:242
port_to_str.port parameter still has values that haven't been 
checked.
  Remaining item(s) declared at...
ha_config_test.c:239
ha_config_test.c:243
new_port parameter still has values that haven't been checked.
  Remaining item(s) declared at...
ha_config_test.c:240
ha_config_test.c:244
[  FAILED ] test__GPHD_HA_load_nodes__PortMissing
[ RUN ] test__GPHD_HA_load_nodes__PortIsInvalidNumber
port_to_str() has remaining non-returned values.
  Remaining item(s) declared at...
ha_config_test.c:277
ha_config_test.c:282
port_to_str() has remaining non-assigned out-values.
  Remaining item(s) declared at...
port:0
port_to_str.port parameter still has values that haven't been 
checked.
  Remaining item(s) declared at...
ha_config_test.c:278
ha_config_test.c:283
new_port parameter still has values that haven't been checked.
  Remaining item(s) declared at...
ha_config_test.c:279
ha_config_test.c:284
[  FAILED ] test__GPHD_HA_load_nodes__PortIsInvalidNumber
[ RUN ] test__GPHD_HA_load_nodes__PortIsNotNumber_TakeOne
port_to_str() has remaining non-returned values.
  Remaining item(s) declared at...
ha_config_test.c:318
ha_config_test.c:323
port_to_str() has remaining non-assigned

[GitHub] incubator-hawq issue #1198: HAWQ-1417. Fixed crash when ANALYZE after COPY b...

2017-03-29 Thread huor 
Github user huor commented on the issue:

https://github.com/apache/incubator-hawq/pull/1198
  
@liming01, the mock file for analyze is generated. The way to add mock is 
at: 
https://github.com/apache/incubator-hawq/blob/master/src/test/unit/README.txt. 
Please take a look and see if it is good to leverage mock for your fix.

The mock test is covered in hawq ci. You can do that in local environment 
also: cd src/backend; make unittest-check

If it is hard to reproduce the issue with sql, I think mock is an option we 
can try.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---