[GitHub] incubator-hawq pull request #1173: HAWQ-1386. Mask some generated files for ...

2017-03-14 Thread paul-guo- 
GitHub user paul-guo- opened a pull request:

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

HAWQ-1386. Mask some generated files for pljava feature testing for git.



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

$ git pull https://github.com/paul-guo-/incubator-hawq test

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

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


commit bc53fc0f708a078bb4d6641af57656d958f4a5cd
Author: Paul Guo 
Date:   2017-03-15T05:23:52Z

HAWQ-1386. Mask some generated files for pljava feature testing for git.




---
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-1378) Elaborate the "invalid command-line arguments for server process" error.

2017-03-14 Thread Paul Guo (JIRA) 

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

Paul Guo closed HAWQ-1378.
--
   Resolution: Fixed
Fix Version/s: 2.2.0.0-incubating

> Elaborate the "invalid command-line arguments for server process" error.
> 
>
> Key: HAWQ-1378
> URL: https://issues.apache.org/jira/browse/HAWQ-1378
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Paul Guo
>Assignee: Paul Guo
> Fix For: 2.2.0.0-incubating
>
>
> I saw the following errors when running several times,
> "Error dispatching to ***: connection pointer is NULL."
> FATAL:  invalid command-line arguments for server process
> While this usually means there is bug in related code but the code should 
> have reported more detailed log so that we could catch what argument is wrong 
> with less pain, even there is log level switch for argument dumping.



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

[GitHub] incubator-hawq pull request #1162: HAWQ-1378. Elaborate the "invalid command...

2017-03-14 Thread paul-guo- 
Github user paul-guo- closed the pull request at:

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


---
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 #1163: HAWQ-1379. Do not send options multiple t...

2017-03-14 Thread paul-guo- 
Github user paul-guo- closed the pull request at:

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


---
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 #1162: HAWQ-1378. Elaborate the "invalid command-line a...

2017-03-14 Thread paul-guo- 
Github user paul-guo- commented on the issue:

https://github.com/apache/incubator-hawq/pull/1162
  
Merged. Closing.


---
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 #1171: HAWQ-1359. Add test cases for Ranger supp...

2017-03-14 Thread linwen 
Github user linwen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1171#discussion_r106084037
  
--- Diff: src/test/feature/Ranger/test_ranger.cpp ---
@@ -24,19 +24,34 @@
 
 #include "lib/command.h"
 #include "lib/gpfdist.h"
-#include "lib/sql_util.h"
 #include "lib/string_util.h"
 
 using std::vector;
 using std::string;
 using hawq::test::SQLUtility;
 using hawq::test::Command;
 
+TestHawqRanger::TestHawqRanger()
+{
+   initfile = hawq::test::stringFormat("Ranger/sql/init_file");
+   rangerHost = getRangerHost();
+}
+
+std::string& TestHawqRanger::getRangerHost()
--- End diff --

The RPS and HAWQ master are required to installed on a same node. This test 
case is to add/remove policy from Ranger Admin, but HAWQ only knows and 
interacts with RPS, it need not configure Ranger Admin address/hostname. 

I am considering still use a environment value to control it.  


---
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 #1171: HAWQ-1359. Add test cases for Ranger supp...

2017-03-14 Thread linwen 
Github user linwen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1171#discussion_r106080149
  
--- Diff: src/test/feature/lib/sql_util.cpp ---
@@ -224,7 +225,9 @@ const string SQLUtility::generateSQLFile(const string 
, bool usingDefaul
 EXPECT_TRUE(false) << "Error opening file " << newSqlFile;
   }
   out << "-- start_ignore" << std::endl;
+  printf("dd2d%s\n",schemaName.c_str());
   if (!usingDefaultSchema) {
+ printf("ddd%s\n",schemaName.c_str());
--- End diff --

Thanks, I will check it. 


---
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 #1171: HAWQ-1359. Add test cases for Ranger supp...

2017-03-14 Thread stanlyxiang 
Github user stanlyxiang commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1171#discussion_r106078845
  
--- Diff: ranger-plugin/.gitignore ---
@@ -1,2 +1,3 @@
 target/
 Makefile.global
+/bin/
--- End diff --

is there any dir "bin" generated by building ? "/bin/" only ignore 
directory "bin" in current directory, e.g ranger-plugin/bin. Recommend "bin/" 
to ignore all "bin" directory from current directory to all sub-directories. 


---
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 #1171: HAWQ-1359. Add test cases for Ranger supp...

2017-03-14 Thread stanlyxiang 
Github user stanlyxiang commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1171#discussion_r106079103
  
--- Diff: src/test/feature/Ranger/test_ranger.cpp ---
@@ -24,19 +24,34 @@
 
 #include "lib/command.h"
 #include "lib/gpfdist.h"
-#include "lib/sql_util.h"
 #include "lib/string_util.h"
 
 using std::vector;
 using std::string;
 using hawq::test::SQLUtility;
 using hawq::test::Command;
 
+TestHawqRanger::TestHawqRanger()
+{
+   initfile = hawq::test::stringFormat("Ranger/sql/init_file");
+   rangerHost = getRangerHost();
+}
+
+std::string& TestHawqRanger::getRangerHost()
--- End diff --

I checked rangeruser.py and found that the "-h" option stands for "ranger 
server host". Since rps won't be installed on ranger server host that usually, 
so I don't think this is a right way to get ranger server host. 


---
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 #1171: HAWQ-1359. Add test cases for Ranger supp...

2017-03-14 Thread stanlyxiang 
Github user stanlyxiang commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1171#discussion_r106078042
  
--- Diff: src/test/feature/Ranger/test_ranger.cpp ---
@@ -24,19 +24,34 @@
 
 #include "lib/command.h"
 #include "lib/gpfdist.h"
-#include "lib/sql_util.h"
 #include "lib/string_util.h"
 
 using std::vector;
 using std::string;
 using hawq::test::SQLUtility;
 using hawq::test::Command;
 
+TestHawqRanger::TestHawqRanger()
+{
+   initfile = hawq::test::stringFormat("Ranger/sql/init_file");
+   rangerHost = getRangerHost();
+}
+
+std::string& TestHawqRanger::getRangerHost()
--- End diff --

Better to get guc value by connecting to db and using sql from pg_settings, 
not hawq config. Using sql could avoid string find and hardcoded number length. 
And hawq config also connect to db and use sql to get the value. 


---
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 #1171: HAWQ-1359. Add test cases for Ranger support, co...

2017-03-14 Thread ictmalili 
Github user ictmalili commented on the issue:

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

[jira] [Commented] (HAWQ-1108) Add JDBC PXF Plugin

2017-03-14 Thread Shivram Mani (JIRA) 

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

Shivram Mani commented on HAWQ-1108:


No problem. 
We will be marking this as a beta only feature until we add the required number 
of automation tests.

> Add JDBC PXF Plugin
> ---
>
> Key: HAWQ-1108
> URL: https://issues.apache.org/jira/browse/HAWQ-1108
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF
>Reporter: Michael Andre Pearce (IG)
>Assignee: Devin Jia
>
> On the back of the work in :
> https://issues.apache.org/jira/browse/HAWQ-779
> We would like to add to Hawq Plugins a JDBC implementation.
> There are currently two noted implementations in the openly available in 
> GitHub.
> 1) https://github.com/kojec/pxf-field/tree/master/jdbc-pxf-ext
> 2) https://github.com/inspur-insight/pxf-plugin/tree/master/pxf-jdbc
> The latter (2) is an improved version of the former (1) and also what 
> HAWQ-779 changes were to support.
> [~jiadx] would you be happy to contribute the source as apache 2 license open 
> source?



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

[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory

2017-03-14 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-1382:
--

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

https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106057640
  
--- Diff: 
markdown/bestpractices/managing_resources_bestpractices.html.md.erb ---
@@ -110,11 +110,14 @@ ALTER RESOURCE queue1 WITH 
(VSEG_RESOURCE_QUOTA='mem:2gb');
 If there are only occasional queries on Parquet tables with a large page 
size, use a statement level specification instead of altering the resource 
queue. For example:
 
 ```sql
-SET HAWQ_RM_STMT_NVSEG=10;
-SET HAWQ_RM_STMT_VSEG_MEMORY='2gb';
-query1;
-SET HAWQ_RM_STMT_NVSEG=0;
+postgres=# SET hawq_rm_stmt_nvseg=10;
+postgres=# SET hawq_rm_stmt_vseg_memory='2gb';
+postgres=# query1;
+postgres=# SET hawq_rm_stmt_nvseg=0;
+postgres=# SET
 ```
+***Note:*** To enable the statement level, you must set 
`hawq_rm_stmt_nvseg` to a value greater than 0 before setting 
`hawq_rm_stmt_vseg_memory`. After running a query or completing the session, 
the value of `hawq_rm_stmt_nvseg` should be reset to 0,  as shown in the 
example above.
--- End diff --

Change "To enable the statement level" to "To set the parameters at the 
statement level"


> Specify necessary setup for hawq_rm_stmt_nvseg and  hawq_rm_stmt_vseg_memory
> 
>
> Key: HAWQ-1382
> URL: https://issues.apache.org/jira/browse/HAWQ-1382
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Jane Beckman
>Assignee: David Yozie
> Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating
>
>
> You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory
> To enable statement level, users must set  hawq_rm_stmt_nvseg to a number 
> larger than 0, run desired query, then set it back.



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

[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory

2017-03-14 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-1382:
--

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

https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106058647
  
--- Diff: 
markdown/bestpractices/managing_resources_bestpractices.html.md.erb ---
@@ -110,11 +110,14 @@ ALTER RESOURCE queue1 WITH 
(VSEG_RESOURCE_QUOTA='mem:2gb');
 If there are only occasional queries on Parquet tables with a large page 
size, use a statement level specification instead of altering the resource 
queue. For example:
 
 ```sql
-SET HAWQ_RM_STMT_NVSEG=10;
-SET HAWQ_RM_STMT_VSEG_MEMORY='2gb';
-query1;
-SET HAWQ_RM_STMT_NVSEG=0;
+postgres=# SET hawq_rm_stmt_nvseg=10;
+postgres=# SET hawq_rm_stmt_vseg_memory='2gb';
+postgres=# query1;
+postgres=# SET hawq_rm_stmt_nvseg=0;
+postgres=# SET
--- End diff --

I'm pretty sure this SET command isn't actually a command to type at the 
postgres=# prompt, but an output from psqsl.  See the example at the end of 
this PR (each SET  command results in psql showing SET).  You should 
make both code blocks similar in this regard.


> Specify necessary setup for hawq_rm_stmt_nvseg and  hawq_rm_stmt_vseg_memory
> 
>
> Key: HAWQ-1382
> URL: https://issues.apache.org/jira/browse/HAWQ-1382
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Jane Beckman
>Assignee: David Yozie
> Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating
>
>
> You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory
> To enable statement level, users must set  hawq_rm_stmt_nvseg to a number 
> larger than 0, run desired query, then set it back.



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

[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory

2017-03-14 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-1382:
--

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

https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106058017
  
--- Diff: markdown/resourcemgmt/ConfigureResourceManagement.html.md.erb ---
@@ -100,22 +100,25 @@ In some cases, you may want to specify additional 
resource quotas on the query s
 
 The following configuration properties allow a user to control resource 
quotas without altering corresponding resource queues.
 
--   
[hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html)
 -   [hawq\_rm\_stmt\_nvseg](../reference/guc/parameter_definitions.html)
+-   
[hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html)
 
 However, the changed resource quota for the virtual segment cannot exceed 
the resource queue’s maximum capacity in HAWQ.
 
+***Note:*** The value of `hawq_rm_stmt_vseg_memory` depends on 
`hawq_rm_stmt_nvseg`, which defines the number of virtual segments used for the 
query. You must set `hawq_rm_stmt_nvseg` to a value greater than 0 before 
setting the memory quota for each segment with  `hawq_rm_stmt_vseg_memory`. 
After running a query or completing the session, the value of 
`hawq_rm_stmt_nvseg` should be reset to 0 to disable the statement level 
resource quota.
--- End diff --

Change "the value of `hawq_rm_stmt_nvseg` should be reset to 0 " to "reset 
the value of `hawq_rm_stmt_nvseg` to 0"


> Specify necessary setup for hawq_rm_stmt_nvseg and  hawq_rm_stmt_vseg_memory
> 
>
> Key: HAWQ-1382
> URL: https://issues.apache.org/jira/browse/HAWQ-1382
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Jane Beckman
>Assignee: David Yozie
> Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating
>
>
> You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory
> To enable statement level, users must set  hawq_rm_stmt_nvseg to a number 
> larger than 0, run desired query, then set it back.



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

[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory

2017-03-14 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-1382:
--

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

https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106058705
  
--- Diff: markdown/resourcemgmt/ConfigureResourceManagement.html.md.erb ---
@@ -100,22 +100,25 @@ In some cases, you may want to specify additional 
resource quotas on the query s
 
 The following configuration properties allow a user to control resource 
quotas without altering corresponding resource queues.
 
--   
[hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html)
 -   [hawq\_rm\_stmt\_nvseg](../reference/guc/parameter_definitions.html)
+-   
[hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html)
 
 However, the changed resource quota for the virtual segment cannot exceed 
the resource queue’s maximum capacity in HAWQ.
 
+***Note:*** The value of `hawq_rm_stmt_vseg_memory` depends on 
`hawq_rm_stmt_nvseg`, which defines the number of virtual segments used for the 
query. You must set `hawq_rm_stmt_nvseg` to a value greater than 0 before 
setting the memory quota for each segment with  `hawq_rm_stmt_vseg_memory`. 
After running a query or completing the session, the value of 
`hawq_rm_stmt_nvseg` should be reset to 0 to disable the statement level 
resource quota.
+
 In the following example, when executing the next query statement, the 
HAWQ resource manager will attempt to allocate 10 virtual segments and each 
segment has a 256MB memory quota.
 
+
 ``` sql
+postgres=# SET hawq_rm_stmt_nvseg=10;
+SET
 postgres=# SET hawq_rm_stmt_vseg_memory='256mb';
 SET
-postgres=# SET hawq_rm_stmt_nvseg=10;
+postgres=# SELECT  FROM  WHERE 
--- End diff --

Should at least terminate this example with a semicolon;


> Specify necessary setup for hawq_rm_stmt_nvseg and  hawq_rm_stmt_vseg_memory
> 
>
> Key: HAWQ-1382
> URL: https://issues.apache.org/jira/browse/HAWQ-1382
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Jane Beckman
>Assignee: David Yozie
> Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating
>
>
> You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory
> To enable statement level, users must set  hawq_rm_stmt_nvseg to a number 
> larger than 0, run desired query, then set it back.



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

[jira] [Closed] (HAWQ-1383) docs - pl/pgsql page cleanup

2017-03-14 Thread Lisa Owen (JIRA) 

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

Lisa Owen closed HAWQ-1383.
---

> docs - pl/pgsql page cleanup
> 
>
> Key: HAWQ-1383
> URL: https://issues.apache.org/jira/browse/HAWQ-1383
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Lisa Owen
>Assignee: David Yozie
> Fix For: 2.2.0.0-incubating
>
>
> various updates to pl/pgsql page:
> - move polymorphic types discussion to a more general section
> - remove dblink reference
> - use actual pl/pgsql examples, not SQL examples
> - other miscellanous clean-up and clarifications



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

[jira] [Commented] (HAWQ-1108) Add JDBC PXF Plugin

2017-03-14 Thread Shivram Mani (JIRA) 

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

Shivram Mani commented on HAWQ-1108:


I've merged it to master.

> Add JDBC PXF Plugin
> ---
>
> Key: HAWQ-1108
> URL: https://issues.apache.org/jira/browse/HAWQ-1108
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF
>Reporter: Michael Andre Pearce (IG)
>Assignee: Devin Jia
>
> On the back of the work in :
> https://issues.apache.org/jira/browse/HAWQ-779
> We would like to add to Hawq Plugins a JDBC implementation.
> There are currently two noted implementations in the openly available in 
> GitHub.
> 1) https://github.com/kojec/pxf-field/tree/master/jdbc-pxf-ext
> 2) https://github.com/inspur-insight/pxf-plugin/tree/master/pxf-jdbc
> The latter (2) is an improved version of the former (1) and also what 
> HAWQ-779 changes were to support.
> [~jiadx] would you be happy to contribute the source as apache 2 license open 
> source?



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

[jira] [Commented] (HAWQ-1108) Add JDBC PXF Plugin

2017-03-14 Thread Shivram Mani (JIRA) 

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

Shivram Mani commented on HAWQ-1108:


Kavinder had very clearly suggested Devin to squash his commits into one commit 
to make it easy for us to merge to master while preserving the original author 
of the code.
We can alternatively do this ourselves and try using git hooks to modify the 
author prior to merge.

> Add JDBC PXF Plugin
> ---
>
> Key: HAWQ-1108
> URL: https://issues.apache.org/jira/browse/HAWQ-1108
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF
>Reporter: Michael Andre Pearce (IG)
>Assignee: Devin Jia
>
> On the back of the work in :
> https://issues.apache.org/jira/browse/HAWQ-779
> We would like to add to Hawq Plugins a JDBC implementation.
> There are currently two noted implementations in the openly available in 
> GitHub.
> 1) https://github.com/kojec/pxf-field/tree/master/jdbc-pxf-ext
> 2) https://github.com/inspur-insight/pxf-plugin/tree/master/pxf-jdbc
> The latter (2) is an improved version of the former (1) and also what 
> HAWQ-779 changes were to support.
> [~jiadx] would you be happy to contribute the source as apache 2 license open 
> source?



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

[jira] [Commented] (HAWQ-1108) Add JDBC PXF Plugin

2017-03-14 Thread Michael Andre Pearce (IG) (JIRA) 

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

Michael Andre Pearce (IG) commented on HAWQ-1108:
-

[~kavinderd] i notice still this hasnt been merged in, can this be merged in as 
is now [~jiadx] has rebased over 6 days ago.

> Add JDBC PXF Plugin
> ---
>
> Key: HAWQ-1108
> URL: https://issues.apache.org/jira/browse/HAWQ-1108
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF
>Reporter: Michael Andre Pearce (IG)
>Assignee: Devin Jia
>
> On the back of the work in :
> https://issues.apache.org/jira/browse/HAWQ-779
> We would like to add to Hawq Plugins a JDBC implementation.
> There are currently two noted implementations in the openly available in 
> GitHub.
> 1) https://github.com/kojec/pxf-field/tree/master/jdbc-pxf-ext
> 2) https://github.com/inspur-insight/pxf-plugin/tree/master/pxf-jdbc
> The latter (2) is an improved version of the former (1) and also what 
> HAWQ-779 changes were to support.
> [~jiadx] would you be happy to contribute the source as apache 2 license open 
> source?



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

[GitHub] incubator-hawq pull request #1172: Hawq 1385. fixed hawq_ctl stop failed whe...

2017-03-14 Thread interma 
Github user interma closed the pull request at:

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


---
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 #1172: Hawq 1385. fixed hawq_ctl stop failed when maste...

2017-03-14 Thread interma 
Github user interma commented on the issue:

https://github.com/apache/incubator-hawq/pull/1172
  
merged


---
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-1385) hawq_ctl stop failed when master is down

2017-03-14 Thread Hongxu Ma (JIRA) 

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

Hongxu Ma closed HAWQ-1385.
---
Resolution: Fixed

fixed

> hawq_ctl stop failed when master is down
> 
>
> Key: HAWQ-1385
> URL: https://issues.apache.org/jira/browse/HAWQ-1385
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Command Line Tools
>Reporter: Hongxu Ma
>Assignee: Hongxu Ma
> Fix For: 2.2.0.0-incubating
>
>
> example (master is down):
> hawq activate standby
> hawq stop allsegments
> error output:
> {code}
> 20170314:03:49:36:005905 
> hawq_activate:centos7-datanode3:gpadmin-[INFO]:-20170314:03:49:36:005933 
> hawq_stop:centos7-datanode3:gpadmin-[ERROR]:-Failed to connect to database, 
> this script can only be run when the database is up
> {code}



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

[GitHub] incubator-hawq issue #1163: HAWQ-1379. Do not send options multiple times in...

2017-03-14 Thread ictmalili 
Github user ictmalili commented on the issue:

https://github.com/apache/incubator-hawq/pull/1163
  
LGTM. +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 #1162: HAWQ-1378. Elaborate the "invalid command-line a...

2017-03-14 Thread paul-guo- 
Github user paul-guo- commented on the issue:

https://github.com/apache/incubator-hawq/pull/1162
  
Yes, and then print the immediate errorrous argument.


---
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 #1172: Hawq 1385. fixed hawq_ctl stop failed when maste...

2017-03-14 Thread linwen 
Github user linwen commented on the issue:

https://github.com/apache/incubator-hawq/pull/1172
  
+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 #1171: HAWQ-1359. Add test cases for Ranger support, co...

2017-03-14 Thread linwen 
Github user linwen commented on the issue:

https://github.com/apache/incubator-hawq/pull/1171
  
It has passed jenkins and travis check, I think it can pass license check. 


---
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 #1172: Hawq 1385. fixed hawq_ctl stop failed whe...

2017-03-14 Thread linwen 
Github user linwen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1172#discussion_r105848316
  
--- Diff: tools/bin/hawq_ctl ---
@@ -835,6 +835,8 @@ class HawqStop:
 acl_type = rows.next()[1]
 conn.close()
 except DatabaseError, ex:
+# get hawq_acl_type from hawq_site.xml if connect db failed.
+# avoid cannot stop segments where master is down.
--- End diff --

This line could be removed. 


---
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 #1172: Hawq 1385. fixed hawq_ctl stop failed whe...

2017-03-14 Thread linwen 
Github user linwen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/1172#discussion_r105848224
  
--- Diff: tools/bin/hawq_ctl ---
@@ -835,6 +835,8 @@ class HawqStop:
 acl_type = rows.next()[1]
 conn.close()
 except DatabaseError, ex:
+# get hawq_acl_type from hawq_site.xml if connect db failed.
--- End diff --

# get hawq_acl_type from local hawq_site.xml if connect master failed.


---
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 #1172: Hawq 1385. fixed hawq_ctl stop failed whe...

2017-03-14 Thread interma 
GitHub user interma opened a pull request:

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

Hawq 1385. fixed hawq_ctl stop failed when master is down

Get hawq_acl_type from hawq_site.xml if connect db failed.


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

$ git pull https://github.com/interma/interma-hawq HAWQ-1385

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

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


commit a0c918e25eb1cb8a677e8942acd9bdcf0473a449
Author: interma 
Date:   2017-03-14T07:28:27Z

fixed hawq_ctl stop failed

commit 7c6089dc5ee75145e741dcd63ff4c0cab3b4cd5d
Author: interma 
Date:   2017-03-14T08:08:41Z

HAWQ-1385. hawq_ctl stop failed when master is down




---
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 #1172: Hawq 1385. fixed hawq_ctl stop failed when maste...

2017-03-14 Thread interma 
Github user interma commented on the issue:

https://github.com/apache/incubator-hawq/pull/1172
  
@linwen @wcl14 @ictmalili help to review, tks!


---
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 #1171: HAWQ-1359. Add test cases for Ranger support, co...

2017-03-14 Thread linwen 
Github user linwen commented on the issue:

https://github.com/apache/incubator-hawq/pull/1171
  
This file already has 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 #1167: PLEASE IGNORE - Test PR to validate Apach...

2017-03-14 Thread edespino 
Github user edespino closed the pull request at:

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


---
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 #1171: HAWQ-1359. Add test cases for Ranger supp...

2017-03-14 Thread linwen 
GitHub user linwen opened a pull request:

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

HAWQ-1359. Add test cases for Ranger support, combinations of differe…

Please review, thanks! 

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

$ git pull https://github.com/linwen/incubator-hawq hawq-1359

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

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


commit dc36e81b3a74d1c04c3b138f6cfc053a657b62d4
Author: Wen Lin 
Date:   2017-03-14T07:17:32Z

HAWQ-1359. Add test cases for Ranger support, combinations of different 
allow/exclude policies.




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