date:20170116

[GitHub] incubator-hawq issue #1073: HAWQ-1248. Merge Dockerfiles for HAWQ Dev into H...

2017-01-16 Thread guofengrichard

Github user guofengrichard commented on the issue:

https://github.com/apache/incubator-hawq/pull/1073
  
These commits have been checked into master of 'apache/incubator-hawq'. So 
close this pull request. 


---
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 #1073: HAWQ-1248. Merge Dockerfiles for HAWQ Dev...

2017-01-16 Thread guofengrichard

Github user guofengrichard closed the pull request at:

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


---
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] [Resolved] (HAWQ-1277) The "make" command generates an error on CentOS 7 when --with-perl is run in configure.

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino resolved HAWQ-1277.
-
Resolution: Fixed

Pushed to master and 2.1.0.0-incubating

> The "make" command generates an error on CentOS 7 when --with-perl is run in 
> configure.
> ---
>
> Key: HAWQ-1277
> URL: https://issues.apache.org/jira/browse/HAWQ-1277
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
> Attachments: plperl-GNUmakefile-xsubpp-rhel7.patch
>
>
> The following "make" error is encountered on CentOS 7 when --with-perl is run 
> in configure:
> {code}
> make[3]: Entering directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
> "/usr/bin/perl" ./text2macro.pl --strip='^(\#.*|\s*)$' 
> plc_perlboot.pl plc_trusted.pl 
> > perlchunks.h
> "/usr/bin/perl" plperl_opmask.pl plperl_opmask.h
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
> /usr/share/perl5/ExtUtils/typemap SPI.xs >SPI.c
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
> /usr/share/perl5/ExtUtils/typemap Util.xs >Util.c
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
> directory
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
> directory
> make[3]: *** [SPI.c] Error 2
> make[3]: *** Deleting file `SPI.c'
> make[3]: *** Waiting for unfinished jobs
> make[3]: *** [Util.c] Error 2
> make[3]: *** Deleting file `Util.c'
> make[3]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
> make[2]: *** [all] Error 1
> make[2]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src'
> make: *** [all] Error 2
> {code}
> I also have found a fix for this which was backported from PostgreSQL to the 
> Greenplum DB master branch a year ago by Heikki 
> Linnakangas (Original PostgreSQL committer 
> Andrew Dunstan mailto:and...@dunslane.net>>):
> https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a153c9f80b9c#diff-97d34e5e3684082069b6c85876df9107



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

[GitHub] incubator-hawq pull request #1091: HAWQ-1277. Fix build problem on CentOS 7,...

2017-01-16 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #1091: HAWQ-1277. Fix build problem on CentOS 7, with -...

2017-01-16 Thread edespino

Github user edespino commented on the issue:

https://github.com/apache/incubator-hawq/pull/1091
  
Thank you!!! @interma & @linwen


---
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 #1091: HAWQ-1277. Fix build problem on CentOS 7, with -...

2017-01-16 Thread linwen

Github user linwen commented on the issue:

https://github.com/apache/incubator-hawq/pull/1091
  
+1 


---
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 #1090: HAWQ-1203. Ranger Plugin Service Implementation....

2017-01-16 Thread denalex

Github user denalex commented on the issue:

https://github.com/apache/incubator-hawq/pull/1090
  
updated the files that were missing licenses, created new PR: 
https://github.com/apache/incubator-hawq/pull/1092


---
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 #1090: HAWQ-1203. Ranger Plugin Service Implemen...

2017-01-16 Thread denalex

Github user denalex closed the pull request at:

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


---
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 #1092: HAWQ-1203. Ranger Plugin Service Implemen...

2017-01-16 Thread denalex

GitHub user denalex opened a pull request:

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

HAWQ-1203. Ranger Plugin Service Implementation. (with contributions â¦

â¦by Lav Jain and Leslie Chang)

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

$ git pull https://github.com/denalex/incubator-hawq ranger-plugin-3

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

https://github.com/apache/incubator-hawq/pull/1092.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 #1092


commit 1f829f7d1c77d140425eca7b02fcb22271ee3430
Author: Alexander Denissov 
Date:   2017-01-16T19:46:36Z

HAWQ-1203. Ranger Plugin Service Implementation. (with contributions by Lav 
Jain and Leslie Chang)




---
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] [Closed] (HAWQ-1267) NOTICE file need to be updated to reflect the right year for copyright

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino closed HAWQ-1267.
---

Merged to master and 2.1.0.0-incubating

> NOTICE file need to be updated to reflect the right year for copyright
> --
>
> Key: HAWQ-1267
> URL: https://issues.apache.org/jira/browse/HAWQ-1267
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0.0-incubating
>Reporter: Ruilong Huo
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
>
> The NOTICE file need to updated to reflect the right year for copyright for 
> apache hawq 2.1.0.0-incubating release.
> To be specific, update
> {noformat}
> Apache HAWQ (incubating)
> Copyright 2016 The Apache Software Foundation.
> {noformat}
> to
> {noformat}
> Apache HAWQ (incubating)
> Copyright 2017 The Apache Software Foundation.
> {noformat}



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

[jira] [Closed] (HAWQ-1268) pom.xml need to be updated to reflect the correct version for apache hawq 2.1.0.0-incubating release

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino closed HAWQ-1268.
---

Merged to master and 2.1.0.0-incubating

> pom.xml need to be updated to reflect the correct version for apache hawq 
> 2.1.0.0-incubating release
> 
>
> Key: HAWQ-1268
> URL: https://issues.apache.org/jira/browse/HAWQ-1268
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0.0-incubating
>Reporter: Ruilong Huo
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
>
> pom.xml need to be updated to reflect the correct version for apache hawq 
> 2.1.0.0-incubating release. Otherwise, RAT check with shows wrong hawq 
> version.
> {noformat}
> rhuo-mbp:apache-hawq-src-2.1.0.0-incubating rhuo$ mvn verify
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building hawq 2.0
> [INFO] 
> 
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.12/apache-rat-plugin-0.12.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.12/apache-rat-plugin-0.12.pom
>  (10 KB at 1.1 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.12/apache-rat-project-0.12.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.12/apache-rat-project-0.12.pom
>  (24 KB at 0.8 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/apache/17/apache-17.pom
> ...
> {noformat}
> To be specific, update
> {noformat}
>   org.apache.hawq
>   hawq
>   2.0
>   pom
> {noformat}
> to
> {noformat}
>   org.apache.hawq
>   hawq
>   2.1
>   pom
> {noformat}



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

[jira] [Resolved] (HAWQ-1268) pom.xml need to be updated to reflect the correct version for apache hawq 2.1.0.0-incubating release

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino resolved HAWQ-1268.
-
Resolution: Fixed

Merged to master and 2.1.0.0-incubating

> pom.xml need to be updated to reflect the correct version for apache hawq 
> 2.1.0.0-incubating release
> 
>
> Key: HAWQ-1268
> URL: https://issues.apache.org/jira/browse/HAWQ-1268
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0.0-incubating
>Reporter: Ruilong Huo
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
>
> pom.xml need to be updated to reflect the correct version for apache hawq 
> 2.1.0.0-incubating release. Otherwise, RAT check with shows wrong hawq 
> version.
> {noformat}
> rhuo-mbp:apache-hawq-src-2.1.0.0-incubating rhuo$ mvn verify
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building hawq 2.0
> [INFO] 
> 
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.12/apache-rat-plugin-0.12.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.12/apache-rat-plugin-0.12.pom
>  (10 KB at 1.1 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.12/apache-rat-project-0.12.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.12/apache-rat-project-0.12.pom
>  (24 KB at 0.8 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/apache/17/apache-17.pom
> ...
> {noformat}
> To be specific, update
> {noformat}
>   org.apache.hawq
>   hawq
>   2.0
>   pom
> {noformat}
> to
> {noformat}
>   org.apache.hawq
>   hawq
>   2.1
>   pom
> {noformat}



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

[jira] [Updated] (HAWQ-1268) pom.xml need to be updated to reflect the correct version for apache hawq 2.1.0.0-incubating release

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino updated HAWQ-1268:

Fix Version/s: 2.2.0.0-incubating

> pom.xml need to be updated to reflect the correct version for apache hawq 
> 2.1.0.0-incubating release
> 
>
> Key: HAWQ-1268
> URL: https://issues.apache.org/jira/browse/HAWQ-1268
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0.0-incubating
>Reporter: Ruilong Huo
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
>
> pom.xml need to be updated to reflect the correct version for apache hawq 
> 2.1.0.0-incubating release. Otherwise, RAT check with shows wrong hawq 
> version.
> {noformat}
> rhuo-mbp:apache-hawq-src-2.1.0.0-incubating rhuo$ mvn verify
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building hawq 2.0
> [INFO] 
> 
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.12/apache-rat-plugin-0.12.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.12/apache-rat-plugin-0.12.pom
>  (10 KB at 1.1 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.12/apache-rat-project-0.12.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.12/apache-rat-project-0.12.pom
>  (24 KB at 0.8 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/apache/17/apache-17.pom
> ...
> {noformat}
> To be specific, update
> {noformat}
>   org.apache.hawq
>   hawq
>   2.0
>   pom
> {noformat}
> to
> {noformat}
>   org.apache.hawq
>   hawq
>   2.1
>   pom
> {noformat}



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

[jira] [Commented] (HAWQ-1268) pom.xml need to be updated to reflect the correct version for apache hawq 2.1.0.0-incubating release

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino commented on HAWQ-1268:
-

Merged to master and 2.1.0.0-incubating

> pom.xml need to be updated to reflect the correct version for apache hawq 
> 2.1.0.0-incubating release
> 
>
> Key: HAWQ-1268
> URL: https://issues.apache.org/jira/browse/HAWQ-1268
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0.0-incubating
>Reporter: Ruilong Huo
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
>
> pom.xml need to be updated to reflect the correct version for apache hawq 
> 2.1.0.0-incubating release. Otherwise, RAT check with shows wrong hawq 
> version.
> {noformat}
> rhuo-mbp:apache-hawq-src-2.1.0.0-incubating rhuo$ mvn verify
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building hawq 2.0
> [INFO] 
> 
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.12/apache-rat-plugin-0.12.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-plugin/0.12/apache-rat-plugin-0.12.pom
>  (10 KB at 1.1 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.12/apache-rat-project-0.12.pom
> Downloaded: 
> https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-project/0.12/apache-rat-project-0.12.pom
>  (24 KB at 0.8 KB/sec)
> Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/apache/17/apache-17.pom
> ...
> {noformat}
> To be specific, update
> {noformat}
>   org.apache.hawq
>   hawq
>   2.0
>   pom
> {noformat}
> to
> {noformat}
>   org.apache.hawq
>   hawq
>   2.1
>   pom
> {noformat}



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

[jira] [Updated] (HAWQ-1267) NOTICE file need to be updated to reflect the right year for copyright

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino updated HAWQ-1267:

Fix Version/s: 2.2.0.0-incubating

> NOTICE file need to be updated to reflect the right year for copyright
> --
>
> Key: HAWQ-1267
> URL: https://issues.apache.org/jira/browse/HAWQ-1267
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0.0-incubating
>Reporter: Ruilong Huo
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
>
> The NOTICE file need to updated to reflect the right year for copyright for 
> apache hawq 2.1.0.0-incubating release.
> To be specific, update
> {noformat}
> Apache HAWQ (incubating)
> Copyright 2016 The Apache Software Foundation.
> {noformat}
> to
> {noformat}
> Apache HAWQ (incubating)
> Copyright 2017 The Apache Software Foundation.
> {noformat}



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

[jira] [Resolved] (HAWQ-1267) NOTICE file need to be updated to reflect the right year for copyright

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino resolved HAWQ-1267.
-
Resolution: Fixed

Merged to master and 2.1.0.0-incubating

> NOTICE file need to be updated to reflect the right year for copyright
> --
>
> Key: HAWQ-1267
> URL: https://issues.apache.org/jira/browse/HAWQ-1267
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.1.0.0-incubating
>Reporter: Ruilong Huo
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
>
> The NOTICE file need to updated to reflect the right year for copyright for 
> apache hawq 2.1.0.0-incubating release.
> To be specific, update
> {noformat}
> Apache HAWQ (incubating)
> Copyright 2016 The Apache Software Foundation.
> {noformat}
> to
> {noformat}
> Apache HAWQ (incubating)
> Copyright 2017 The Apache Software Foundation.
> {noformat}



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

[jira] [Updated] (HAWQ-1272) Modify code sample to use standard SQL syntax

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino updated HAWQ-1272:

Fix Version/s: (was: 2.1.0.0-incubating)
   2.2.0.0-incubating

> Modify code sample to use standard SQL syntax
> -
>
> Key: HAWQ-1272
> URL: https://issues.apache.org/jira/browse/HAWQ-1272
> Project: Apache HAWQ
>  Issue Type: Improvement
>Reporter: Jane Beckman
>Assignee: Ed Espino
> Fix For: 2.2.0.0-incubating
>
>
> Parts of the code sample for checking table size should be uppercase.



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

[jira] [Commented] (HAWQ-1278) Investigate installcheck-good issue on Mac OSX

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino commented on HAWQ-1278:
-

FYI: The hcatalog_lookup test suite requires "hive" and "pxf" services running. 
 The following SQL will cause a core dump on my MacBook Pro (Mac OS Sierra 
10.12.2 and Xcode 8.2.1):

{code}
SELECT * FROM pxf_get_item_fields('Hive', '*');
{code}

> Investigate installcheck-good issue on Mac OSX
> --
>
> Key: HAWQ-1278
> URL: https://issues.apache.org/jira/browse/HAWQ-1278
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Tests
>Reporter: Ed Espino
>Assignee: Ruilong Huo
> Fix For: 2.1.0.0-incubating
>
>
> I am filing this as a place holder for the Mac OSX installcheck-good 
> investigation work.  Ming Li originally reported installcheck-good testing 
> issues with errtable and hcatalog_lookup test suites.
> This issue is not seen on CentOS 6 & 7 environments.



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

[jira] [Updated] (HAWQ-1278) Investigate installcheck-good issue on Mac OSX

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino updated HAWQ-1278:

Assignee: Ruilong Huo  (was: Ed Espino)

> Investigate installcheck-good issue on Mac OSX
> --
>
> Key: HAWQ-1278
> URL: https://issues.apache.org/jira/browse/HAWQ-1278
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Tests
>Reporter: Ed Espino
>Assignee: Ruilong Huo
> Fix For: 2.1.0.0-incubating
>
>
> I am filing this as a place holder for the Mac OSX installcheck-good 
> investigation work.  Ming Li originally reported installcheck-good testing 
> issues with errtable and hcatalog_lookup test suites.
> This issue is not seen on CentOS 6 & 7 environments.



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

[jira] [Assigned] (HAWQ-1278) Investigate installcheck-good issue on Mac OSX

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino reassigned HAWQ-1278:
---

Assignee: Ed Espino  (was: Jiali Yao)

> Investigate installcheck-good issue on Mac OSX
> --
>
> Key: HAWQ-1278
> URL: https://issues.apache.org/jira/browse/HAWQ-1278
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Tests
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating
>
>
> I am filing this as a place holder for the Mac OSX installcheck-good 
> investigation work.  Ming Li originally reported installcheck-good testing 
> issues with errtable and hcatalog_lookup test suites.
> This issue is not seen on CentOS 6 & 7 environments.



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

[jira] [Created] (HAWQ-1278) Investigate installcheck-good issue on Mac OSX

2017-01-16 Thread Ed Espino (JIRA)

Ed Espino created HAWQ-1278:
---

 Summary: Investigate installcheck-good issue on Mac OSX
 Key: HAWQ-1278
 URL: https://issues.apache.org/jira/browse/HAWQ-1278
 Project: Apache HAWQ
  Issue Type: Task
  Components: Tests
Reporter: Ed Espino
Assignee: Jiali Yao
 Fix For: 2.1.0.0-incubating


I am filing this as a place holder for the Mac OSX installcheck-good 
investigation work.  Ming Li originally reported installcheck-good testing 
issues with errtable and hcatalog_lookup test suites.

This issue is not seen on CentOS 6 & 7 environments.



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

[GitHub] incubator-hawq pull request #1090: HAWQ-1203. Ranger Plugin Service Implemen...

2017-01-16 Thread stanlyxiang

Github user stanlyxiang commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1090#discussion_r96338779
  
--- Diff: 
ranger-plugin/integration/service/src/test/java/org/apache/hawq/ranger/integration/service/tests/RPSRequest.java
 ---
@@ -0,0 +1,41 @@
+package org.apache.hawq.ranger.integration.service.tests;
--- End diff --

license header 


---
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 #1090: HAWQ-1203. Ranger Plugin Service Implemen...

2017-01-16 Thread stanlyxiang

Github user stanlyxiang commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1090#discussion_r96338796
  
--- Diff: 
ranger-plugin/integration/service/src/test/java/org/apache/hawq/ranger/integration/service/tests/RPSResponse.java
 ---
@@ -0,0 +1,23 @@
+package org.apache.hawq.ranger.integration.service.tests;
--- End diff --

license header


---
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 #1090: HAWQ-1203. Ranger Plugin Service Implemen...

2017-01-16 Thread stanlyxiang

Github user stanlyxiang commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1090#discussion_r96338825
  
--- Diff: 
ranger-plugin/integration/service/src/test/java/org/apache/hawq/ranger/integration/service/tests/Utils.java
 ---
@@ -0,0 +1,57 @@
+package org.apache.hawq.ranger.integration.service.tests;
--- End diff --

license header


---
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] [Commented] (HAWQ-1277) The "make" command generates an error on CentOS 7 when --with-perl is run in configure.

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino commented on HAWQ-1277:
-

Pull Request has been submitted: 
https://github.com/apache/incubator-hawq/pull/1091

> The "make" command generates an error on CentOS 7 when --with-perl is run in 
> configure.
> ---
>
> Key: HAWQ-1277
> URL: https://issues.apache.org/jira/browse/HAWQ-1277
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
> Attachments: plperl-GNUmakefile-xsubpp-rhel7.patch
>
>
> The following "make" error is encountered on CentOS 7 when --with-perl is run 
> in configure:
> {code}
> make[3]: Entering directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
> "/usr/bin/perl" ./text2macro.pl --strip='^(\#.*|\s*)$' 
> plc_perlboot.pl plc_trusted.pl 
> > perlchunks.h
> "/usr/bin/perl" plperl_opmask.pl plperl_opmask.h
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
> /usr/share/perl5/ExtUtils/typemap SPI.xs >SPI.c
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
> /usr/share/perl5/ExtUtils/typemap Util.xs >Util.c
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
> directory
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
> directory
> make[3]: *** [SPI.c] Error 2
> make[3]: *** Deleting file `SPI.c'
> make[3]: *** Waiting for unfinished jobs
> make[3]: *** [Util.c] Error 2
> make[3]: *** Deleting file `Util.c'
> make[3]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
> make[2]: *** [all] Error 1
> make[2]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src'
> make: *** [all] Error 2
> {code}
> I also have found a fix for this which was backported from PostgreSQL to the 
> Greenplum DB master branch a year ago by Heikki 
> Linnakangas (Original PostgreSQL committer 
> Andrew Dunstan mailto:and...@dunslane.net>>):
> https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a153c9f80b9c#diff-97d34e5e3684082069b6c85876df9107



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

[GitHub] incubator-hawq issue #1091: HAWQ-1277. Fix build problem on CentOS 7, with -...

2017-01-16 Thread interma

Github user interma commented on the issue:

https://github.com/apache/incubator-hawq/pull/1091
  
+1 
I also tested on mac, no problem.


---
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 #1091: HAWQ-1277. Fix build problem on CentOS 7,...

2017-01-16 Thread edespino

GitHub user edespino opened a pull request:

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

HAWQ-1277. Fix build problem on CentOS 7, with --with-plperl.

Please see HAWQ-1277 for additional details.

This fix was originally backported from PostgreSQL to the Greenplum DB 
master branch a year ago by Heikki Linnakangas 
(Original PostgreSQL committer Andrew Dunstan 
mailto:and...@dunslane.net>>):


https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a153c9f80b9c#diff-97d34e5e3684082069b6c85876df9107

See earlier discussion on this on pgsql-hackers, message-id
9b946296-a2eb-4b45-a190-153f06662...@kineticode.com. We'd get this fix
eventually as we merge with later PostgreSQL versions, but let's make life
easier for people hitting this issue now.

This is a backpatch of the following upstream commit, sans the MSVC build
parts, as I have no environment to test that and we don't support Windows
anyway. We'll get the MSVC parts later, as we merge.

commit ba00ab0b111a0cbbac612e8ea8b0d5f96534102e
Author: Andrew Dunstan 
Date:   Sat Nov 26 15:22:32 2011 -0500

Use the preferred version of xsubpp, not necessarily the one that came 
with the
distro version of perl.

David Wheeler and Alex Hunsaker.

Backpatch to 9.1 where it applies cleanly. A simple workaround is 
available for earlier
branches, and further effort doesn't seem warranted.

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

$ git pull https://github.com/edespino/incubator-hawq HAWQ-1277

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

https://github.com/apache/incubator-hawq/pull/1091.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 #1091


commit 1aa7e59d57b164bd7d85f9d7b7aba3977679324b
Author: Ed Espino 
Date:   2017-01-17T02:55:18Z

HAWQ-1277. Fix build problem on CentOS 7, with --with-plperl.

See earlier discussion on this on pgsql-hackers, message-id
9b946296-a2eb-4b45-a190-153f06662...@kineticode.com. We'd get this fix
eventually as we merge with later PostgreSQL versions, but let's make life
easier for people hitting this issue now.

This is a backpatch of the following upstream commit, sans the MSVC build
parts, as I have no environment to test that and we don't support Windows
anyway. We'll get the MSVC parts later, as we merge.

commit ba00ab0b111a0cbbac612e8ea8b0d5f96534102e
Author: Andrew Dunstan 
Date:   Sat Nov 26 15:22:32 2011 -0500

Use the preferred version of xsubpp, not necessarily the one that came 
with the
distro version of perl.

David Wheeler and Alex Hunsaker.

Backpatch to 9.1 where it applies cleanly. A simple workaround is 
available for earlier
branches, and further effort doesn't seem warranted.




---
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] [Updated] (HAWQ-1277) The "make" command generates an error on CentOS 7 when --with-perl is run in configure.

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino updated HAWQ-1277:

Attachment: plperl-GNUmakefile-xsubpp-rhel7.patch

Here is a patch that will correct this issue.

> The "make" command generates an error on CentOS 7 when --with-perl is run in 
> configure.
> ---
>
> Key: HAWQ-1277
> URL: https://issues.apache.org/jira/browse/HAWQ-1277
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
> Attachments: plperl-GNUmakefile-xsubpp-rhel7.patch
>
>
> The following "make" error is encountered on CentOS 7 when --with-perl is run 
> in configure:
> {code}
> make[3]: Entering directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
> "/usr/bin/perl" ./text2macro.pl --strip='^(\#.*|\s*)$' 
> plc_perlboot.pl plc_trusted.pl 
> > perlchunks.h
> "/usr/bin/perl" plperl_opmask.pl plperl_opmask.h
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
> /usr/share/perl5/ExtUtils/typemap SPI.xs >SPI.c
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
> /usr/share/perl5/ExtUtils/typemap Util.xs >Util.c
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
> directory
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
> directory
> make[3]: *** [SPI.c] Error 2
> make[3]: *** Deleting file `SPI.c'
> make[3]: *** Waiting for unfinished jobs
> make[3]: *** [Util.c] Error 2
> make[3]: *** Deleting file `Util.c'
> make[3]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
> make[2]: *** [all] Error 1
> make[2]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src'
> make: *** [all] Error 2
> {code}
> I also have found a fix for this which was backported from PostgreSQL to the 
> Greenplum DB master branch a year ago by Heikki 
> Linnakangas (Original PostgreSQL committer 
> Andrew Dunstan mailto:and...@dunslane.net>>):
> https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a153c9f80b9c#diff-97d34e5e3684082069b6c85876df9107



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

[jira] [Updated] (HAWQ-1277) The "make" command generates an error on CentOS 7 when --with-perl is run in configure.

2017-01-16 Thread Ed Espino (JIRA)


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

Ed Espino updated HAWQ-1277:

Fix Version/s: 2.2.0.0-incubating

> The "make" command generates an error on CentOS 7 when --with-perl is run in 
> configure.
> ---
>
> Key: HAWQ-1277
> URL: https://issues.apache.org/jira/browse/HAWQ-1277
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.1.0.0-incubating, 2.2.0.0-incubating
>
>
> The following "make" error is encountered on CentOS 7 when --with-perl is run 
> in configure:
> {code}
> make[3]: Entering directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
> "/usr/bin/perl" ./text2macro.pl --strip='^(\#.*|\s*)$' 
> plc_perlboot.pl plc_trusted.pl 
> > perlchunks.h
> "/usr/bin/perl" plperl_opmask.pl plperl_opmask.h
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
> /usr/share/perl5/ExtUtils/typemap SPI.xs >SPI.c
> "/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
> /usr/share/perl5/ExtUtils/typemap Util.xs >Util.c
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
> directory
> Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
> directory
> make[3]: *** [SPI.c] Error 2
> make[3]: *** Deleting file `SPI.c'
> make[3]: *** Waiting for unfinished jobs
> make[3]: *** [Util.c] Error 2
> make[3]: *** Deleting file `Util.c'
> make[3]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
> make[2]: *** [all] Error 1
> make[2]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory 
> `/home/centos/apache-hawq-src-2.1.0.0-incubating/src'
> make: *** [all] Error 2
> {code}
> I also have found a fix for this which was backported from PostgreSQL to the 
> Greenplum DB master branch a year ago by Heikki 
> Linnakangas (Original PostgreSQL committer 
> Andrew Dunstan mailto:and...@dunslane.net>>):
> https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a153c9f80b9c#diff-97d34e5e3684082069b6c85876df9107



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

[jira] [Created] (HAWQ-1277) The "make" command generates an error on CentOS 7 when --with-perl is run in configure.

2017-01-16 Thread Ed Espino (JIRA)

Ed Espino created HAWQ-1277:
---

 Summary: The "make" command generates an error on CentOS 7 when 
--with-perl is run in configure.
 Key: HAWQ-1277
 URL: https://issues.apache.org/jira/browse/HAWQ-1277
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Build
Reporter: Ed Espino
Assignee: Ed Espino
 Fix For: 2.1.0.0-incubating


The following "make" error is encountered on CentOS 7 when --with-perl is run 
in configure:

{code}
make[3]: Entering directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
"/usr/bin/perl" ./text2macro.pl --strip='^(\#.*|\s*)$' 
plc_perlboot.pl plc_trusted.pl > 
perlchunks.h
"/usr/bin/perl" plperl_opmask.pl plperl_opmask.h
"/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
/usr/share/perl5/ExtUtils/typemap SPI.xs >SPI.c
"/usr/bin/perl" /usr/share/perl5/ExtUtils/xsubpp -typemap 
/usr/share/perl5/ExtUtils/typemap Util.xs >Util.c
Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
directory
Can't open perl script "/usr/share/perl5/ExtUtils/xsubpp": No such file or 
directory
make[3]: *** [SPI.c] Error 2
make[3]: *** Deleting file `SPI.c'
make[3]: *** Waiting for unfinished jobs
make[3]: *** [Util.c] Error 2
make[3]: *** Deleting file `Util.c'
make[3]: Leaving directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl/plperl'
make[2]: *** [all] Error 1
make[2]: Leaving directory 
`/home/centos/apache-hawq-src-2.1.0.0-incubating/src/pl'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/centos/apache-hawq-src-2.1.0.0-incubating/src'
make: *** [all] Error 2
{code}

I also have found a fix for this which was backported from PostgreSQL to the 
Greenplum DB master branch a year ago by Heikki 
Linnakangas (Original PostgreSQL committer Andrew 
Dunstan mailto:and...@dunslane.net>>):

https://github.com/greenplum-db/gpdb/commit/f493756a5ac8a90ff1d5e3b84f38a153c9f80b9c#diff-97d34e5e3684082069b6c85876df9107



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

[jira] [Commented] (HAWQ-1261) docs - log files discussion

2017-01-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-1261:
--

GitHub user lisakowen opened a pull request:

https://github.com/apache/incubator-hawq-docs/pull/88

HAWQ-1261 - add discussion of HAWQ administrative log files

added a discussion of HAWQ log files.  restructured some existing content.  
added new subnav entry.

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

$ git pull https://github.com/lisakowen/incubator-hawq-docs 
feature/HAWQ-1261-logfiles

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

https://github.com/apache/incubator-hawq-docs/pull/88.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 #88


commit 44217fabb9185d75b3ad07f0bbd2d5e754b2d466
Author: Lisa Owen 
Date:   2017-01-11T02:06:36Z

new topic on logfiles and associated changes

commit dfd893655845c71d4f42e720d4876d6b48b2d2ed
Author: Lisa Owen 
Date:   2017-01-12T23:56:01Z

add subnav for new logfiles topic




> docs - log files discussion
> ---
>
> Key: HAWQ-1261
> URL: https://issues.apache.org/jira/browse/HAWQ-1261
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Lisa Owen
>Assignee: David Yozie
>Priority: Minor
>
> info about viewing server log files is embedded in the "Monitoring a HAWQ 
> System" topic.  pull this topic out into it's own page, add info about other 
> (hawq admin utilities) log files, and provide more info and some relevant 
> examples.



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

[jira] [Commented] (HAWQ-1263) docs - miscellaneous improvements

2017-01-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-1263:
--

Github user lisakowen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96321794
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
--- End diff --

i think template0 and template1 start out the same.  you cannot modify 
template0, but you can template1.


> docs - miscellaneous improvements
> -
>
> Key: HAWQ-1263
> URL: https://issues.apache.org/jira/browse/HAWQ-1263
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Lisa Owen
>Assignee: David Yozie
>Priority: Minor
>
> ambari rest api:
>   - add warning about using http delete requests
>   - use AMBARI instead of AMB in env varbs for clarity
>   - add link from main ambari doc to rest apis and adjust subnav accordingly
> intro to hawq op env:
>  - include info about PATH and LD_LIBRARY_PATH settings
>  - add pxf log file directory to table of important files/dirs
> gpfdist:
>  - correct example for single instance
> aws configuration
>  - more info re: storage types and security groups
>  - update instance types table
> ddl database
>  - clarify that you can only clone from a template database
>  - various other wording and formatting fixes



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

[jira] [Commented] (HAWQ-1263) docs - miscellaneous improvements

2017-01-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-1263:
--

Github user dyozie commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96318167
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
 
 ## Creating a Database 
 
-The `CREATE DATABASE` command creates a new database. For example:
+You must have appropriate privileges or be a HAWQ superuser to create a 
database. If you do not have the correct privileges, you cannot create a 
database. The HAWQ administrator must either grant you the necessary privileges 
or create a database for you.
+
+The [CREATE DATABASE](../reference/sql/CREATE-DATABASE.html) command 
creates a new database. For example:
 
 ``` sql
-=> CREATE DATABASE new_dbname;
+=# CREATE DATABASE ;
 ```
 
-To create a database, you must have privileges to create a database or be 
a HAWQ superuser. If you do not have the correct privileges, you cannot create 
a database. The HAWQ administrator must either give you the necessary 
privileges or to create a database for you.
-
-You can also use the client program `createdb` to create a database. For 
example, running the following command in a command line terminal connects to 
HAWQ using the provided host name and port and creates a database named 
*mydatabase*:
+You can also use the client program `createdb` to create a database. For 
example, running the following command connects to HAWQ on the host named 
`hmaster` at port `5432` and creates a database named `mydatabase`:
 
 ``` shell
-$ createdb -h masterhost -p 5432 mydatabase
+$ createdb -h hmaster -p 5432 mydatabase
 ```
 
-The host name and port must match the host name and port of the installed 
HAWQ system.
+The host name and port must match the host name and port of the HAWQ 
master node.
 
-Some objects, such as roles, are shared by all the databases in a HAWQ 
system. Other objects, such as tables that you create, are known only in the 
database in which you create them.
+Some objects, such as roles, are shared by all of the databases in a HAWQ 
deployment. Other objects, such as tables that you create, are known only to 
the database in which you create them.
 
 ### Cloning a Database 
 
-By default, a new database is created by cloning the standard system 
database template, *template1*. Any database can b

[jira] [Commented] (HAWQ-1263) docs - miscellaneous improvements

2017-01-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-1263:
--

Github user dyozie commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96318306
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
 
 ## Creating a Database 
 
-The `CREATE DATABASE` command creates a new database. For example:
+You must have appropriate privileges or be a HAWQ superuser to create a 
database. If you do not have the correct privileges, you cannot create a 
database. The HAWQ administrator must either grant you the necessary privileges 
or create a database for you.
+
+The [CREATE DATABASE](../reference/sql/CREATE-DATABASE.html) command 
creates a new database. For example:
 
 ``` sql
-=> CREATE DATABASE new_dbname;
+=# CREATE DATABASE ;
 ```
 
-To create a database, you must have privileges to create a database or be 
a HAWQ superuser. If you do not have the correct privileges, you cannot create 
a database. The HAWQ administrator must either give you the necessary 
privileges or to create a database for you.
-
-You can also use the client program `createdb` to create a database. For 
example, running the following command in a command line terminal connects to 
HAWQ using the provided host name and port and creates a database named 
*mydatabase*:
+You can also use the client program `createdb` to create a database. For 
example, running the following command connects to HAWQ on the host named 
`hmaster` at port `5432` and creates a database named `mydatabase`:
 
 ``` shell
-$ createdb -h masterhost -p 5432 mydatabase
+$ createdb -h hmaster -p 5432 mydatabase
 ```
 
-The host name and port must match the host name and port of the installed 
HAWQ system.
+The host name and port must match the host name and port of the HAWQ 
master node.
 
-Some objects, such as roles, are shared by all the databases in a HAWQ 
system. Other objects, such as tables that you create, are known only in the 
database in which you create them.
+Some objects, such as roles, are shared by all of the databases in a HAWQ 
deployment. Other objects, such as tables that you create, are known only to 
the database in which you create them.
 
 ### Cloning a Database 
 
-By default, a new database is created by cloning the standard system 
database template, *template1*. Any database can b

[jira] [Commented] (HAWQ-1263) docs - miscellaneous improvements

2017-01-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-1263:
--

Github user dyozie commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96318754
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
 
 ## Creating a Database 
 
-The `CREATE DATABASE` command creates a new database. For example:
+You must have appropriate privileges or be a HAWQ superuser to create a 
database. If you do not have the correct privileges, you cannot create a 
database. The HAWQ administrator must either grant you the necessary privileges 
or create a database for you.
+
+The [CREATE DATABASE](../reference/sql/CREATE-DATABASE.html) command 
creates a new database. For example:
 
 ``` sql
-=> CREATE DATABASE new_dbname;
+=# CREATE DATABASE ;
 ```
 
-To create a database, you must have privileges to create a database or be 
a HAWQ superuser. If you do not have the correct privileges, you cannot create 
a database. The HAWQ administrator must either give you the necessary 
privileges or to create a database for you.
-
-You can also use the client program `createdb` to create a database. For 
example, running the following command in a command line terminal connects to 
HAWQ using the provided host name and port and creates a database named 
*mydatabase*:
+You can also use the client program `createdb` to create a database. For 
example, running the following command connects to HAWQ on the host named 
`hmaster` at port `5432` and creates a database named `mydatabase`:
 
 ``` shell
-$ createdb -h masterhost -p 5432 mydatabase
+$ createdb -h hmaster -p 5432 mydatabase
 ```
 
-The host name and port must match the host name and port of the installed 
HAWQ system.
+The host name and port must match the host name and port of the HAWQ 
master node.
 
-Some objects, such as roles, are shared by all the databases in a HAWQ 
system. Other objects, such as tables that you create, are known only in the 
database in which you create them.
+Some objects, such as roles, are shared by all of the databases in a HAWQ 
deployment. Other objects, such as tables that you create, are known only to 
the database in which you create them.
 
 ### Cloning a Database 
 
-By default, a new database is created by cloning the standard system 
database template, *template1*. Any database can b

[jira] [Commented] (HAWQ-1263) docs - miscellaneous improvements

2017-01-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-1263:
--

Github user dyozie commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96317760
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
 
 ## Creating a Database 
 
-The `CREATE DATABASE` command creates a new database. For example:
+You must have appropriate privileges or be a HAWQ superuser to create a 
database. If you do not have the correct privileges, you cannot create a 
database. The HAWQ administrator must either grant you the necessary privileges 
or create a database for you.
+
+The [CREATE DATABASE](../reference/sql/CREATE-DATABASE.html) command 
creates a new database. For example:
 
 ``` sql
-=> CREATE DATABASE new_dbname;
+=# CREATE DATABASE ;
 ```
 
-To create a database, you must have privileges to create a database or be 
a HAWQ superuser. If you do not have the correct privileges, you cannot create 
a database. The HAWQ administrator must either give you the necessary 
privileges or to create a database for you.
-
-You can also use the client program `createdb` to create a database. For 
example, running the following command in a command line terminal connects to 
HAWQ using the provided host name and port and creates a database named 
*mydatabase*:
+You can also use the client program `createdb` to create a database. For 
example, running the following command connects to HAWQ on the host named 
`hmaster` at port `5432` and creates a database named `mydatabase`:
 
 ``` shell
-$ createdb -h masterhost -p 5432 mydatabase
+$ createdb -h hmaster -p 5432 mydatabase
 ```
 
-The host name and port must match the host name and port of the installed 
HAWQ system.
+The host name and port must match the host name and port of the HAWQ 
master node.
 
-Some objects, such as roles, are shared by all the databases in a HAWQ 
system. Other objects, such as tables that you create, are known only in the 
database in which you create them.
+Some objects, such as roles, are shared by all of the databases in a HAWQ 
deployment. Other objects, such as tables that you create, are known only to 
the database in which you create them.
 
 ### Cloning a Database 
 
-By default, a new database is created by cloning the standard system 
database template, *template1*. Any database can b

[jira] [Commented] (HAWQ-1263) docs - miscellaneous improvements

2017-01-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-1263:
--

Github user dyozie commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/86#discussion_r96317322
  
--- Diff: markdown/ddl/ddl-database.html.md.erb ---
@@ -2,77 +2,75 @@
 title: Creating and Managing Databases
 ---
 
-A HAWQ system is a single instance of HAWQ. There can be several separate 
HAWQ systems installed, but usually just one is selected by environment 
variable settings. See your HAWQ administrator for details.
-
-There can be multiple databases in a HAWQ system. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
+Your HAWQ deployment may have multiple databases. This is different from 
some database management systems \(such as Oracle\) where the database instance 
*is* the database. Although you can create many databases in a HAWQ system, 
client programs can connect to and access only one database at a time — you 
cannot cross-query between databases.
 
 ## About Template Databases 
 
-Each new database you create is based on a *template*. HAWQ provides a 
default database, *template1*. Use *template1* to connect to HAWQ for the first 
time. HAWQ uses *template1* to create databases unless you specify another 
template. Do not create any objects in *template1* unless you want those 
objects to be in every database you create.
+Each new database you create is based on a *template*. HAWQ provides a 
default database, `template1`. HAWQ uses `template1` to create databases unless 
you specify another template. Do not create any objects in `template1` unless 
you want those objects to be in every database you create.
 
-HAWQ uses two other database templates, *template0* and *postgres*, 
internally. Do not drop or modify *template0* or *postgres*. You can use 
*template0* to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you modified 
*template1*.
+HAWQ uses two other database templates internally, `template0` and 
`postgres`. Do not drop or modify `template0` or `postgres`. You can use 
`template0` to create a completely clean database containing only the standard 
objects predefined by HAWQ at initialization, especially if you have modified 
`template1`.
--- End diff --

", especially if you have modified `template1`" -> ". This may be necessary 
if you have modified `template1`."

This also implies that template0 and template1 are the same - is that 
correct?


> docs - miscellaneous improvements
> -
>
> Key: HAWQ-1263
> URL: https://issues.apache.org/jira/browse/HAWQ-1263
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Lisa Owen
>Assignee: David Yozie
>Priority: Minor
>
> ambari rest api:
>   - add warning about using http delete requests
>   - use AMBARI instead of AMB in env varbs for clarity
>   - add link from main ambari doc to rest apis and adjust subnav accordingly
> intro to hawq op env:
>  - include info about PATH and LD_LIBRARY_PATH settings
>  - add pxf log file directory to table of important files/dirs
> gpfdist:
>  - correct example for single instance
> aws configuration
>  - more info re: storage types and security groups
>  - update instance types table
> ddl database
>  - clarify that you can only clone from a template database
>  - various other wording and formatting fixes



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

[jira] [Commented] (HAWQ-1251) Add CREATE CAST/CONVERSION pages to documentation

2017-01-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-1251:
--

Github user janebeckman closed the pull request at:

https://github.com/apache/incubator-hawq-docs/pull/85


> Add CREATE CAST/CONVERSION pages to documentation
> -
>
> Key: HAWQ-1251
> URL: https://issues.apache.org/jira/browse/HAWQ-1251
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Jane Beckman
>Assignee: David Yozie
>
> The pg_cast table, created by CREATE CAST is already in the documentation, 
> but not the command. Testing shows CREATE CAST seems to be supported in HAWQ.



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

[GitHub] incubator-hawq pull request #1085: HAWQ-1203. Ranger Plugin Service Implemen...

2017-01-16 Thread denalex

Github user denalex closed the pull request at:

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


---
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 #1090: HAWQ-1203. Ranger Plugin Service Implemen...

2017-01-16 Thread denalex

GitHub user denalex opened a pull request:

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

HAWQ-1203. Ranger Plugin Service Implementation. (with contributions â¦

â¦by Lav Jain and Leslie Chang)

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

$ git pull https://github.com/denalex/incubator-hawq ranger-plugin-2

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

https://github.com/apache/incubator-hawq/pull/1090.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 #1090


commit 003d182aba3d3a327afc89eab5385b70594a46cd
Author: Alexander Denissov 
Date:   2017-01-16T19:46:36Z

HAWQ-1203. Ranger Plugin Service Implementation. (with contributions by Lav 
Jain and Leslie Chang)




---
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] [Updated] (HAWQ-1263) docs - miscellaneous improvements

2017-01-16 Thread Lisa Owen (JIRA)


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

Lisa Owen updated HAWQ-1263:

Description: 
ambari rest api:
  - add warning about using http delete requests
  - use AMBARI instead of AMB in env varbs for clarity
  - add link from main ambari doc to rest apis and adjust subnav accordingly

intro to hawq op env:
 - include info about PATH and LD_LIBRARY_PATH settings
 - add pxf log file directory to table of important files/dirs

gpfdist:
 - correct example for single instance

aws configuration
 - more info re: storage types and security groups
 - update instance types table

ddl database
 - clarify that you can only clone from a template database
 - various other wording and formatting fixes

  was:
ambari rest api:
  - add warning about using http delete requests
  - use AMBARI instead of AMB in env varbs for clarity
  - add link from main ambari doc to rest apis and adjust subnav accordingly

intro to hawq op env:
 - include info about PATH and LD_LIBRARY_PATH settings
 - add pxf log file directory to table of important files/dirs


> docs - miscellaneous improvements
> -
>
> Key: HAWQ-1263
> URL: https://issues.apache.org/jira/browse/HAWQ-1263
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Lisa Owen
>Assignee: David Yozie
>Priority: Minor
>
> ambari rest api:
>   - add warning about using http delete requests
>   - use AMBARI instead of AMB in env varbs for clarity
>   - add link from main ambari doc to rest apis and adjust subnav accordingly
> intro to hawq op env:
>  - include info about PATH and LD_LIBRARY_PATH settings
>  - add pxf log file directory to table of important files/dirs
> gpfdist:
>  - correct example for single instance
> aws configuration
>  - more info re: storage types and security groups
>  - update instance types table
> ddl database
>  - clarify that you can only clone from a template database
>  - various other wording and formatting fixes



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

[jira] [Resolved] (HAWQ-1252) PL/Java doc page - validate and enhance info

2017-01-16 Thread Lisa Owen (JIRA)


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

Lisa Owen resolved HAWQ-1252.
-
   Resolution: Fixed
Fix Version/s: 2.1.0.0-incubating

PR merged; resolving and closing.

> PL/Java doc page - validate and enhance info
> 
>
> Key: HAWQ-1252
> URL: https://issues.apache.org/jira/browse/HAWQ-1252
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Lisa Owen
>Assignee: David Yozie
>Priority: Minor
> Fix For: 2.1.0.0-incubating
>
>
> PL/Java docs section:
> - review and validate current content
> - make sure examples run and are relevant
> - develop new examples as appropriate



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

[GitHub] incubator-hawq pull request #1089: HAWQ-1243. Add suffix name for ranger res...

2017-01-16 Thread zhangh43

GitHub user zhangh43 opened a pull request:

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

HAWQ-1243. Add suffix name for ranger restful service.

change the default RPS RESTFUL service suffix to rps

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

$ git pull https://github.com/zhangh43/incubator-hawq hawq12431

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

https://github.com/apache/incubator-hawq/pull/1089.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 #1089


commit ec7b4d9e96834d86a1a7196c17e5068c
Author: hubertzhang 
Date:   2017-01-16T09:13:38Z

HAWQ-1243. Add suffix name for ranger restful service.




---
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 #1089: HAWQ-1243. Add suffix name for ranger restful se...

2017-01-16 Thread linwen

Github user linwen commented on the issue:

https://github.com/apache/incubator-hawq/pull/1089
  
+1 


---
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 #1089: HAWQ-1243. Add suffix name for ranger res...

2017-01-16 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #1089: HAWQ-1243. Add suffix name for ranger restful se...

2017-01-16 Thread stanlyxiang

Github user stanlyxiang commented on the issue:

https://github.com/apache/incubator-hawq/pull/1089
  
+1


---
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 #1088: HAWQ-1276. The error message is not frien...

2017-01-16 Thread stanlyxiang

Github user stanlyxiang commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1088#discussion_r96181179
  
--- Diff: src/backend/libpq/rangerrest.c ---
@@ -366,7 +365,7 @@ static size_t write_callback(char *contents, size_t 
size, size_t nitems,
if (curl->response.buffer == NULL)
{
/* out of memory! */
-   elog(WARNING, "not enough memory for Ranger response");
+   elog(WARNING, "cannot allocate memory for ranger response");
--- End diff --

sure. fixed. 


---
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 #1088: HAWQ-1276. The error message is not frien...

2017-01-16 Thread wcl14

Github user wcl14 commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1088#discussion_r96180237
  
--- Diff: src/backend/libpq/rangerrest.c ---
@@ -366,7 +365,7 @@ static size_t write_callback(char *contents, size_t 
size, size_t nitems,
if (curl->response.buffer == NULL)
{
/* out of memory! */
-   elog(WARNING, "not enough memory for Ranger response");
+   elog(WARNING, "cannot allocate memory for ranger response");
--- End diff --

So should the comment be consistent with the code?


---
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 #1088: HAWQ-1276. The error message is not frien...

2017-01-16 Thread stanlyxiang

Github user stanlyxiang commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1088#discussion_r96179729
  
--- Diff: src/backend/libpq/rangerrest.c ---
@@ -366,7 +365,7 @@ static size_t write_callback(char *contents, size_t 
size, size_t nitems,
if (curl->response.buffer == NULL)
{
/* out of memory! */
-   elog(WARNING, "not enough memory for Ranger response");
+   elog(WARNING, "cannot allocate memory for ranger response");
--- End diff --

hmm, IMO , not enough memory is not the only error that will occur. There 
maybe other errors  in the repalloc implementation. So I changed the messages.  


---
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 #1088: HAWQ-1276. The error message is not friendly whe...

2017-01-16 Thread interma

Github user interma commented on the issue:

https://github.com/apache/incubator-hawq/pull/1088
  
+1


---
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 #1088: HAWQ-1276. The error message is not frien...

2017-01-16 Thread wcl14

Github user wcl14 commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1088#discussion_r96178079
  
--- Diff: src/backend/libpq/rangerrest.c ---
@@ -366,7 +365,7 @@ static size_t write_callback(char *contents, size_t 
size, size_t nitems,
if (curl->response.buffer == NULL)
{
/* out of memory! */
-   elog(WARNING, "not enough memory for Ranger response");
+   elog(WARNING, "cannot allocate memory for ranger response");
--- End diff --

Why do you modify the out of memory error message. I think the original one 
is more specified, and may be better.


---
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.
---

51 matches

Mail list logo