[GitHub] incubator-hawq issue #872: HAWQ-1030. Forward PostgreSQL spin lock peformanc...

[linwen]

Github user linwen commented on the issue:

https://github.com/apache/incubator-hawq/pull/872
  
+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] [Created] (HAWQ-1032) Bucket number of new added partition is not consistent with parent table.

[Hubert Zhang (JIRA)]

Hubert Zhang created HAWQ-1032:
--

 Summary: Bucket number of new added partition is not consistent 
with parent table.
 Key: HAWQ-1032
 URL: https://issues.apache.org/jira/browse/HAWQ-1032
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Core
Reporter: Hubert Zhang
Assignee: Lei Chang


Failure Case
set deafult_hash_table_bucket_number = 12;
CREATE TABLE sales3 (id int, date date, amt decimal(10,2)) DISTRIBUTED 
BY (id)   PARTITION BY 
RANGE (date) ( START (date 
'2008-01-01') INCLUSIVEEND (date 
'2009-01-01') EXCLUSIVE EVERY 
(INTERVAL '1 day') );

set deafult_hash_table_bucket_number = 16;
ALTER TABLE sales3 ADD PARTITION   START (date 
'2009-03-01') INCLUSIVE   END (date 
'2009-04-01') EXCLUSIVE;

The new added partition with bukcet number 16 which is not consistent with 
parent partition.



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

[jira] [Assigned] (HAWQ-1032) Bucket number of new added partition is not consistent with parent table.

[Hubert Zhang (JIRA)]

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

Hubert Zhang reassigned HAWQ-1032:
--

Assignee: Hubert Zhang  (was: Lei Chang)

> Bucket number of new added partition is not consistent with parent table.
> -
>
> Key: HAWQ-1032
> URL: https://issues.apache.org/jira/browse/HAWQ-1032
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Core
>Reporter: Hubert Zhang
>Assignee: Hubert Zhang
>
> Failure Case
> set deafult_hash_table_bucket_number = 12;
> CREATE TABLE sales3 (id int, date date, amt decimal(10,2)) 
> DISTRIBUTED BY (id)   
> PARTITION BY RANGE (date) 
> ( START (date '2008-01-01') INCLUSIVE 
>END (date '2009-01-01') EXCLUSIVE  
>EVERY (INTERVAL '1 day') );
> set deafult_hash_table_bucket_number = 16;
> ALTER TABLE sales3 ADD PARTITION   START 
> (date '2009-03-01') INCLUSIVE   END 
> (date '2009-04-01') EXCLUSIVE;
> The new added partition with bukcet number 16 which is not consistent with 
> parent partition.



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

[jira] [Updated] (HAWQ-991) "HAWQ register" could register tables according to .yml configuration file

[Lili Ma (JIRA)]

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

Lili Ma updated HAWQ-991:
-
Summary: "HAWQ register" could register tables according to .yml 
configuration file  (was: Add support for "HAWQ register" that could register 
tables by using "hawq extract" output)

> "HAWQ register" could register tables according to .yml configuration file
> --
>
> Key: HAWQ-991
> URL: https://issues.apache.org/jira/browse/HAWQ-991
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Command Line Tools, External Tables
>Affects Versions: 2.0.1.0-incubating
>Reporter: hongwu
>Assignee: hongwu
> Fix For: 2.0.1.0-incubating
>
>
> Scenario: 
> 1. For cluster Disaster Recovery. Two clusters co-exist, periodically import 
> data from Cluster A to Cluster B. Need Register data to Cluster B.
> 2. For the rollback of table. Do checkpoints somewhere, and need to rollback 
> to previous checkpoint. 
> Description:
> Register according to .yml configuration file. 
> hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-c 
> config] [--force][--repair]  
> Behaviors:
> 1. If table doesn't exist, will automatically create the table and register 
> the files in .yml configuration file. Will use the filesize specified in .yml 
> to update the catalog table. 
> 2. If table already exist, and neither --force nor --repair configured. Do 
> not create any table, and directly register the files specified in .yml file 
> to the table. Note that if the file is under table directory in HDFS, will 
> throw error, say, to-be-registered files should not under the table path.
> 3. If table already exist, and --force is specified. Will clear all the 
> catalog contents in pg_aoseg.pg_paqseg_$relid while keep the files on HDFS, 
> and then re-register all the files to the table.  This is for scenario 2.
> 4. If table already exist, and --repair is specified. Will change both file 
> folder and catalog table pg_aoseg.pg_paqseg_$relid to the state which .yml 
> file configures. Note may some new generated files since the checkpoint may 
> be deleted here. Also note the all the files in .yml file should all under 
> the table folder on HDFS. Limitation: Do not support cases for hash table 
> redistribution, table truncate and table drop. This is for scenario 3.
> Requirements:
> 1. To be registered file path has to colocate with HAWQ in the same HDFS 
> cluster.
> 2. If to be registered is a hash table, the registered file number should be 
> one or multiple times or hash table bucket number.



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

[jira] [Commented] (HAWQ-760) Hawq register

[Lili Ma (JIRA)]

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

Lili Ma commented on HAWQ-760:
--

hawq register has two usages, 
1. Register a file/folder to an existing table. Can register a file or a 
folder. If we register a file, can specify eof of this file. If eof not 
specified, directly use actual file size. If we register a folder, directly use 
actual file size.
hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-f 
filepath] [-e eof]
2. Register according to .yml configuration file. 
hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-c 
config] [--force][--repair]  

HAWQ-991 is the second usage specifying registering according to .yml 
configuration file.

> Hawq register
> -
>
> Key: HAWQ-760
> URL: https://issues.apache.org/jira/browse/HAWQ-760
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Command Line Tools
>Reporter: Yangcheng Luo
>Assignee: Lili Ma
> Fix For: backlog
>
>
> Users sometimes want to register data files generated by other system like 
> hive into hawq. We should add register function to support registering 
> file(s) generated by other system like hive into hawq. So users could 
> integrate their external file(s) into hawq conveniently.



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

[jira] [Updated] (HAWQ-760) Hawq register

[Lili Ma (JIRA)]

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

Lili Ma updated HAWQ-760:
-
Description: 
Scenario: 
1. Register a parquet file generated by other systems, such as Hive, Spark, etc.
2. For cluster Disaster Recovery. Two clusters co-exist, periodically import 
data from Cluster A to Cluster B. Need Register data to Cluster B.
3. For the rollback of table. Do checkpoints somewhere, and need to rollback to 
previous checkpoint. 

Usage1
Description
Register a file/folder to an existing table. Can register a file or a folder. 
If we register a file, can specify eof of this file. If eof not specified, 
directly use actual file size. If we register a folder, directly use actual 
file size.
hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-f 
filepath] [-e eof]


Usage 2
Description
Register according to .yml configuration file. 
hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-c 
config] [--force][--repair]  

Behavior:
1. If table doesn't exist, will automatically create the table and register the 
files in .yml configuration file. Will use the filesize specified in .yml to 
update the catalog table. 

2. If table already exist, and neither --force nor --repair configured. Do not 
create any table, and directly register the files specified in .yml file to the 
table. Note that if the file is under table directory in HDFS, will throw 
error, say, to-be-registered files should not under the table path.

3. If table already exist, and --force is specified. Will clear all the catalog 
contents in pg_aoseg.pg_paqseg_$relid while keep the files on HDFS, and then 
re-register all the files to the table.  This is for scenario 2.

4. If table already exist, and --repair is specified. Will change both file 
folder and catalog table pg_aoseg.pg_paqseg_$relid to the state which .yml file 
configures. Note may some new generated files since the checkpoint may be 
deleted here. Also note the all the files in .yml file should all under the 
table folder on HDFS. Limitation: Do not support cases for hash table 
redistribution, table truncate and table drop. This is for scenario 3.

Requirements for both the cases:
1. To be registered file path has to colocate with HAWQ in the same HDFS 
cluster.
2. If to be registered is a hash table, the registered file number should be 
one or multiple times or hash table bucket number.

  was:Users sometimes want to register data files generated by other system 
like hive into hawq. We should add register function to support registering 
file(s) generated by other system like hive into hawq. So users could integrate 
their external file(s) into hawq conveniently.


> Hawq register
> -
>
> Key: HAWQ-760
> URL: https://issues.apache.org/jira/browse/HAWQ-760
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Command Line Tools
>Reporter: Yangcheng Luo
>Assignee: Lili Ma
> Fix For: backlog
>
>
> Scenario: 
> 1. Register a parquet file generated by other systems, such as Hive, Spark, 
> etc.
> 2. For cluster Disaster Recovery. Two clusters co-exist, periodically import 
> data from Cluster A to Cluster B. Need Register data to Cluster B.
> 3. For the rollback of table. Do checkpoints somewhere, and need to rollback 
> to previous checkpoint. 
> Usage1
> Description
> Register a file/folder to an existing table. Can register a file or a folder. 
> If we register a file, can specify eof of this file. If eof not specified, 
> directly use actual file size. If we register a folder, directly use actual 
> file size.
> hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-f 
> filepath] [-e eof]
> Usage 2
> Description
> Register according to .yml configuration file. 
> hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-c 
> config] [--force][--repair]  
> Behavior:
> 1. If table doesn't exist, will automatically create the table and register 
> the files in .yml configuration file. Will use the filesize specified in .yml 
> to update the catalog table. 
> 2. If table already exist, and neither --force nor --repair configured. Do 
> not create any table, and directly register the files specified in .yml file 
> to the table. Note that if the file is under table directory in HDFS, will 
> throw error, say, to-be-registered files should not under the table path.
> 3. If table already exist, and --force is specified. Will clear all the 
> catalog contents in pg_aoseg.pg_paqseg_$relid while keep the files on HDFS, 
> and then re-register all the files to the table.  This is for scenario 2.
> 4. If table already exist, and --repair is specified. Will change both file 
> folder and catalog table pg_aoseg.pg_paqseg_$relid to the state which .yml 
> file configures. Note may some new generated files 

[jira] [Resolved] (HAWQ-1030) User hang due to poor spin-lock/LWLock performance under high concurrency

[Ming LI (JIRA)]

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

Ming LI resolved HAWQ-1030.
---
Resolution: Fixed

> User hang due to poor spin-lock/LWLock performance under high concurrency
> -
>
> Key: HAWQ-1030
> URL: https://issues.apache.org/jira/browse/HAWQ-1030
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Core
>Reporter: Ming LI
>Assignee: Ming LI
> Fix For: 2.0.1.0-incubating
>
>
> Some clients have recently reported apparent hangs with their applications. 
> In all cases the symptoms were the same:
> * All sessions appear to be hung in LWLockAcquire or Release, specifically 
> s_lock
> * there is a high number of concurrent sessions (close to 100)
> * System is not actually hung, normally processing resumes after some period 
> of time when all sessions have completed their locking work
> The postgresql developer community has found several issues with performance 
> under high concurrency (> 32 sessions) in the spin-lock mechanism we've 
> inherited in HAWQ. This ultimately has been corrected in 9.5 with a 
> replacement to the spin-lock mechanism and appears to provide a significant 
> boost to query performance.
> The actual fix is in commit: ab5194e6f617a9a9e7aadb3dd1cee948a42d0755
> Only 1 line commit to s_lock.c could help address this and would be easy 
> enough to cherry-pick: b03d196be055450c7260749f17347c2d066b4254



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

[GitHub] incubator-hawq pull request #872: HAWQ-1030. Forward PostgreSQL spin lock pe...

[liming01]

Github user liming01 closed the pull request at:

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


---
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-1030) User hang due to poor spin-lock/LWLock performance under high concurrency

[Ming LI (JIRA)]

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

Ming LI commented on HAWQ-1030:
---

Hawq didn't change the implementation of spin lock which is same with 
postgresql, thinking that porting from new version of postgresql in the future, 
here we keep the code more similar to latest postgresql (version 9.6).

> User hang due to poor spin-lock/LWLock performance under high concurrency
> -
>
> Key: HAWQ-1030
> URL: https://issues.apache.org/jira/browse/HAWQ-1030
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Core
>Reporter: Ming LI
>Assignee: Ming LI
> Fix For: 2.0.1.0-incubating
>
>
> Some clients have recently reported apparent hangs with their applications. 
> In all cases the symptoms were the same:
> * All sessions appear to be hung in LWLockAcquire or Release, specifically 
> s_lock
> * there is a high number of concurrent sessions (close to 100)
> * System is not actually hung, normally processing resumes after some period 
> of time when all sessions have completed their locking work
> The postgresql developer community has found several issues with performance 
> under high concurrency (> 32 sessions) in the spin-lock mechanism we've 
> inherited in HAWQ. This ultimately has been corrected in 9.5 with a 
> replacement to the spin-lock mechanism and appears to provide a significant 
> boost to query performance.
> The actual fix is in commit: ab5194e6f617a9a9e7aadb3dd1cee948a42d0755
> Only 1 line commit to s_lock.c could help address this and would be easy 
> enough to cherry-pick: b03d196be055450c7260749f17347c2d066b4254



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

[jira] [Updated] (HAWQ-991) Add support for "HAWQ register" that could register tables by using "hawq extract" output

[Lili Ma (JIRA)]

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

Lili Ma updated HAWQ-991:
-
Description: 
Scenario: 
1. For cluster Disaster Recovery. Two clusters co-exist, periodically import 
data from Cluster A to Cluster B. Need Register data to Cluster B.
2. For the rollback of table. Do checkpoints somewhere, and need to rollback to 
previous checkpoint. 

Description:
Register according to .yml configuration file. 
hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-c 
config] [--force][--repair]  

Behaviors:
1. If table doesn't exist, will automatically create the table and register the 
files in .yml configuration file. Will use the filesize specified in .yml to 
update the catalog table. 

2. If table already exist, and neither --force nor --repair configured. Do not 
create any table, and directly register the files specified in .yml file to the 
table. Note that if the file is under table directory in HDFS, will throw 
error, say, to-be-registered files should not under the table path.

3. If table already exist, and --force is specified. Will clear all the catalog 
contents in pg_aoseg.pg_paqseg_$relid while keep the files on HDFS, and then 
re-register all the files to the table.  This is for scenario 2.

4. If table already exist, and --repair is specified. Will change both file 
folder and catalog table pg_aoseg.pg_paqseg_$relid to the state which .yml file 
configures. Note may some new generated files since the checkpoint may be 
deleted here. Also note the all the files in .yml file should all under the 
table folder on HDFS. Limitation: Do not support cases for hash table 
redistribution, table truncate and table drop. This is for scenario 3.

Requirements:
1. To be registered file path has to colocate with HAWQ in the same HDFS 
cluster.
2. If to be registered is a hash table, the registered file number should be 
one or multiple times or hash table bucket number.



  was:
User should be able to use hawq register to register table files into a new 
HAWQ cluster. It is some kind of protecting against corruption from users' 
perspective. Users use the last-known-good metadata to update the portion of 
catalog managing HDFS blocks. The table files or dictionary should be 
backuped(such as using distcp) into the same path in the new HDFS setting. And 
in this case, both AO and Parquet formats are supported.

Usage:
hawq extract -o t1.yml t1; // in HAWQ Cluster A
hawq register -h localhost -p 5432 -u me -d postgres -c t1.yml t1; // in HAWQ 
Cluster B



> Add support for "HAWQ register" that could register tables by using "hawq 
> extract" output
> -
>
> Key: HAWQ-991
> URL: https://issues.apache.org/jira/browse/HAWQ-991
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Command Line Tools, External Tables
>Affects Versions: 2.0.1.0-incubating
>Reporter: hongwu
>Assignee: hongwu
> Fix For: 2.0.1.0-incubating
>
>
> Scenario: 
> 1. For cluster Disaster Recovery. Two clusters co-exist, periodically import 
> data from Cluster A to Cluster B. Need Register data to Cluster B.
> 2. For the rollback of table. Do checkpoints somewhere, and need to rollback 
> to previous checkpoint. 
> Description:
> Register according to .yml configuration file. 
> hawq register [-h hostname] [-p port] [-U username] [-d databasename] [-c 
> config] [--force][--repair]  
> Behaviors:
> 1. If table doesn't exist, will automatically create the table and register 
> the files in .yml configuration file. Will use the filesize specified in .yml 
> to update the catalog table. 
> 2. If table already exist, and neither --force nor --repair configured. Do 
> not create any table, and directly register the files specified in .yml file 
> to the table. Note that if the file is under table directory in HDFS, will 
> throw error, say, to-be-registered files should not under the table path.
> 3. If table already exist, and --force is specified. Will clear all the 
> catalog contents in pg_aoseg.pg_paqseg_$relid while keep the files on HDFS, 
> and then re-register all the files to the table.  This is for scenario 2.
> 4. If table already exist, and --repair is specified. Will change both file 
> folder and catalog table pg_aoseg.pg_paqseg_$relid to the state which .yml 
> file configures. Note may some new generated files since the checkpoint may 
> be deleted here. Also note the all the files in .yml file should all under 
> the table folder on HDFS. Limitation: Do not support cases for hash table 
> redistribution, table truncate and table drop. This is for scenario 3.
> Requirements:
> 1. To be registered file path has to colocate with HAWQ in the same HDFS 
> cluster.
> 2. If to be registered is a hash table, the 

[jira] [Assigned] (HAWQ-1029) hawq register --help information not correct

[hongwu (JIRA)]

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

hongwu reassigned HAWQ-1029:


Assignee: hongwu  (was: Lei Chang)

> hawq register --help information not correct
> 
>
> Key: HAWQ-1029
> URL: https://issues.apache.org/jira/browse/HAWQ-1029
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Command Line Tools
>Reporter: Lili Ma
>Assignee: hongwu
> Fix For: 2.0.1.0-incubating
>
>
> The example for usage case 1 is not correct, should modify it.
> $ hawq register postgres parquet_table hdfs://localhost:8020/temp/hive.paq



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

[jira] [Commented] (HAWQ-1031) updates docs to reflect MASTER_DATA_DIRECTORY code changes

[Paul Guo (JIRA)]

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

Paul Guo commented on HAWQ-1031:


CC-ing Radar. Assume the doc change is to align with the following patch.

commit 2c1710cee35ba97a9d7278f428dd06d566baf269
Author: rlei 
Date:   Thu Aug 25 17:13:36 2016 +0800

HAWQ-1009  Remove requirement of environment value MASTER_DATA_DIRECTORY





> updates docs to reflect MASTER_DATA_DIRECTORY code changes
> --
>
> Key: HAWQ-1031
> URL: https://issues.apache.org/jira/browse/HAWQ-1031
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.0.1.0-incubating
>Reporter: Lisa Owen
>Assignee: Lei Chang
>Priority: Minor
> Fix For: 2.0.1.0-incubating
>
>
> MASTER_DATA_DIRECTORY is no longer a required environment variable for any 
> HAWQ command.  remove references in the docs, and point users to the 
> hawq-site.xml hawq_master_directory property value when required.



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

[GitHub] incubator-hawq issue #872: HAWQ-1030. Forward PostgreSQL spin lock peformanc...

[paul-guo-]

Github user paul-guo- commented on the issue:

https://github.com/apache/incubator-hawq/pull/872
  
+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 #872: HAWQ-1030. Forward PostgreSQL spin lock peformanc...

[liming01]

Github user liming01 commented on the issue:

https://github.com/apache/incubator-hawq/pull/872
  
Agree, maybe we can post it into posgresql mail list for further discussion.


---
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 #876: HAWQ-1018. Add feature test for goh_gp_dis...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #876: HAWQ-1018. Add feature test for goh_gp_dist_rando...

[zhangh43]

Github user zhangh43 commented on the issue:

https://github.com/apache/incubator-hawq/pull/876
  
+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 #876: HAWQ-1018. Add feature test for goh_gp_dist_rando...

[ztao1987]

Github user ztao1987 commented on the issue:

https://github.com/apache/incubator-hawq/pull/876
  
+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 #876: HAWQ-1018. Add feature test for goh_gp_dis...

[wengyanqing]

GitHub user wengyanqing opened a pull request:

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

HAWQ-1018. Add feature test for goh_gp_dist_random with new test fram…

…ework

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

$ git pull https://github.com/wengyanqing/incubator-hawq HAWQ-1018

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

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


commit 569f7545d289a396f9c002bb304b613a89c3cfc1
Author: ivan 
Date:   2016-08-30T01:52:52Z

HAWQ-1018. Add feature test for goh_gp_dist_random with new test framework




---
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-1015) Add feature test for transactions with new test framework

[Ivan Weng (JIRA)]

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

Ivan Weng resolved HAWQ-1015.
-
Resolution: Fixed

> Add feature test for transactions with new test framework
> -
>
> Key: HAWQ-1015
> URL: https://issues.apache.org/jira/browse/HAWQ-1015
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Tests
>Reporter: Ivan Weng
>Assignee: Ivan Weng
> Fix For: 2.0.1.0-incubating
>
>




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

[GitHub] incubator-hawq issue #875: HAWQ-1015. Add feature test for transactions with...

[ztao1987]

Github user ztao1987 commented on the issue:

https://github.com/apache/incubator-hawq/pull/875
  
+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 #875: HAWQ-1015. Add feature test for transactio...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #875: HAWQ-1015. Add feature test for transactions with...

[zhangh43]

Github user zhangh43 commented on the issue:

https://github.com/apache/incubator-hawq/pull/875
  
+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 #875: HAWQ-1015. Add feature test for transactio...

[wengyanqing]

GitHub user wengyanqing opened a pull request:

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

HAWQ-1015. Add feature test for transactions with new test framework



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

$ git pull https://github.com/wengyanqing/incubator-hawq HAWQ-1015PR

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

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


commit cb80c333176e38a29eba618b70440b12f1b4ab33
Author: ivan 
Date:   2016-08-29T03:01:31Z

HAWQ-1015. Add feature test for transactions with new test framework




---
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-256) Integrate Security with Apache Ranger

[Lili Ma (JIRA)]

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

Lili Ma updated HAWQ-256:
-
Attachment: (was: HAWQRangerSupportDesign_v0.2.pdf)

> Integrate Security with Apache Ranger
> -
>
> Key: HAWQ-256
> URL: https://issues.apache.org/jira/browse/HAWQ-256
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF, Security
>Reporter: Michael Andre Pearce (IG)
>Assignee: Lili Ma
> Fix For: backlog
>
> Attachments: HAWQRangerSupportDesign.pdf, 
> HAWQRangerSupportDesign_v0.2.pdf
>
>
> Integrate security with Apache Ranger for a unified Hadoop security solution. 



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

[jira] [Updated] (HAWQ-256) Integrate Security with Apache Ranger

[Hubert Zhang (JIRA)]

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

Hubert Zhang updated HAWQ-256:
--
Attachment: HAWQRangerSupportDesign_v0.2.pdf

> Integrate Security with Apache Ranger
> -
>
> Key: HAWQ-256
> URL: https://issues.apache.org/jira/browse/HAWQ-256
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF, Security
>Reporter: Michael Andre Pearce (IG)
>Assignee: Lili Ma
> Fix For: backlog
>
> Attachments: HAWQRangerSupportDesign.pdf, 
> HAWQRangerSupportDesign_v0.2.pdf, HAWQRangerSupportDesign_v0.2.pdf
>
>
> Integrate security with Apache Ranger for a unified Hadoop security solution. 



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

[GitHub] incubator-hawq issue #871: HAWQ-909. Add feature test for goh_database with ...

[zhangh43]

Github user zhangh43 commented on the issue:

https://github.com/apache/incubator-hawq/pull/871
  
+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 #871: HAWQ-909. Add feature test for goh_database with ...

[ztao1987]

Github user ztao1987 commented on the issue:

https://github.com/apache/incubator-hawq/pull/871
  
+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 #874: Remove Thrift 0.9.3 from source tree - HAWQ-959

[paul-guo-]

Github user paul-guo- commented on the issue:

https://github.com/apache/incubator-hawq/pull/874
  
Hi ed, I guess the concen comes from the binaries only. I'm wondering
whether we could just remove those binaries (probably need to hack a bit)
to workaround the issue? Besides, if we want to remove thrift, we need to
undo the related work in configure/configure.in also (e.g. the
--with-thrift option), probably there are more things to undo (you could
refer to the original patch which adds the thrift support) please
double-check.

2016-08-30 6:19 GMT+08:00 Ed Espino :

>
>- We will need to update documentation to provide guidance on building
>supporte Thrift version (0.9.3).
>
> --
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/apache/incubator-hawq/pull/874
> Commit Summary
>
>- Remove Thrift from source tree - HAWQ-959
>
> File Changes
>
>- *M* depends/thirdparty/README
> (3)
>- *D* depends/thirdparty/thrift/.clang-format
> (56)
>- *D* depends/thirdparty/thrift/.editorconfig
> (112)
>- *D* depends/thirdparty/thrift/.gitattributes
> (1)
>- *D* depends/thirdparty/thrift/.gitignore
> (280)
>- *D* depends/thirdparty/thrift/.travis.yml
> (188)
>- *D* depends/thirdparty/thrift/CHANGES
>
>(1779)
>- *D* depends/thirdparty/thrift/CMakeLists.txt
> (103)
>- *D* depends/thirdparty/thrift/CONTRIBUTING.md
> (49)
>- *D* depends/thirdparty/thrift/LICENSE
> (253)
>- *D* depends/thirdparty/thrift/Makefile.am
>
>(110)
>- *D* depends/thirdparty/thrift/NOTICE
> (5)
>- *D* depends/thirdparty/thrift/README.md
>
>(164)
>- *D* depends/thirdparty/thrift/aclocal/ac_prog_bison.m4
> (54)
>- *D* depends/thirdparty/thrift/aclocal/ax_boost_base.m4
>
>(272)
>- *D* depends/thirdparty/thrift/aclocal/ax_check_openssl.m4
>
>(124)
>- *D* depends/thirdparty/thrift/aclocal/ax_cxx_compile_stdcxx_11.m4
>
>(165)
>- *D* depends/thirdparty/thrift/aclocal/ax_dmd.m4
>
>(107)
>- *D* depends/thirdparty/thrift/aclocal/ax_javac_and_java.m4
>
>(129)
>- *D* depends/thirdparty/thrift/aclocal/ax_lib_event.m4
>
>(194)
>- *D* depends/thirdparty/thrift/aclocal/ax_lib_zlib.m4
>
>(173)
>- *D* depends/thirdparty/thrift/aclocal/ax_lua.m4
>
>(663)
>- *D* depends/thirdparty/thrift/aclocal/ax_prog_haxe_version.m4
> (60)
>- *D* depends/thirdparty/thrift/aclocal/ax_prog_perl_modules.m4
> (77)
>- *D* depends/thirdparty/thrift/aclocal/ax_signed_right_shift.m4
>
>(127)
>- *D* depends/thirdparty/thrift/aclocal/ax_thrift_internal.m4
> (28)
>- *D* depends/thirdparty/thrift/aclocal/m4_ax_compare_version.m4
>
>(177)
>- *D* 

[jira] [Commented] (HAWQ-959) Clean up Binary files based on RAT reports

[Ed Espino (JIRA)]

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

Ed Espino commented on HAWQ-959:


When this is migrated to master branch, we will need to update CI build process 
to build Thrift 0.9.3 from source and use the artifacts for HAWQ build.

> Clean up Binary files based on RAT reports
> --
>
> Key: HAWQ-959
> URL: https://issues.apache.org/jira/browse/HAWQ-959
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Build
>Affects Versions: 2.0.0.0-incubating
>Reporter: Goden Yao
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating
>
>
> From [~jmclean] and [~alangates] IPMC release candidate review
> An unexpected binary in the source code base:
> depends/thirdparty/thrift/lib/erl/rebar
> There might be others given rat reports 770+ binary files
> We need to clean them up or make exceptions for them with solid reasons.



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

[jira] [Commented] (HAWQ-959) Clean up Binary files based on RAT reports

[Ed Espino (JIRA)]

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

Ed Espino commented on HAWQ-959:


I have submitted a pull request to remove the Thrift 0.9.3 third-party 
dependency files.  We need to provide documentation for building this component 
from source and how to incorporate it into the HAWQ build.

> Clean up Binary files based on RAT reports
> --
>
> Key: HAWQ-959
> URL: https://issues.apache.org/jira/browse/HAWQ-959
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Build
>Affects Versions: 2.0.0.0-incubating
>Reporter: Goden Yao
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating
>
>
> From [~jmclean] and [~alangates] IPMC release candidate review
> An unexpected binary in the source code base:
> depends/thirdparty/thrift/lib/erl/rebar
> There might be others given rat reports 770+ binary files
> We need to clean them up or make exceptions for them with solid reasons.



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

[GitHub] incubator-hawq pull request #874: Remove Thrift 0.9.3 from source tree - HAW...

[edespino]

GitHub user edespino opened a pull request:

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

Remove Thrift 0.9.3 from source tree - HAWQ-959

* We will need to update documentation to provide guidance on building
  supporte Thrift version (0.9.3).

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

$ git pull https://github.com/edespino/incubator-hawq 
2.0.0.0-incubating-HAWQ-959

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

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


commit 7a26202fe8c1082213a92f31d4bd79dab142291b
Author: Ed Espino 
Date:   2016-08-29T22:15:00Z

Remove Thrift from source tree - HAWQ-959

* We will need to update documentation to provide guidance on building
  supporte Thrift version (0.9.3).




---
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-1028) Add '-d' option for hawq state to be compatible with Ambari

[Lisa Owen (JIRA)]

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

Lisa Owen commented on HAWQ-1028:
-

i assume we do not want the "added back in" -d option on hawq state to be 
visible to the user (i.e. documented).  is this a correct assumption?

> Add '-d' option for hawq state to be compatible with Ambari
> ---
>
> Key: HAWQ-1028
> URL: https://issues.apache.org/jira/browse/HAWQ-1028
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Command Line Tools
>Reporter: Radar Lei
>Assignee: Radar Lei
> Fix For: 2.0.1.0-incubating
>
>
> Previously we removed the legacy option '-d' '--datadir' from 'hawq state' 
> command. This option is used to specify the master data directory, but we 
> never used it in our command line tools.
> Now we found this unused option is used by current version Ambari, and will 
> cause Ambari check HAWQ status failed if we removed it. So to be compatible 
> with Ambari, we need to add it back until Ambari do not use this option.



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

[jira] [Resolved] (HAWQ-1006) Fix RPM compliance in Redhat Satellite

[Goden Yao (JIRA)]

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

Goden Yao resolved HAWQ-1006.
-
Resolution: Fixed

> Fix RPM compliance in Redhat Satellite
> --
>
> Key: HAWQ-1006
> URL: https://issues.apache.org/jira/browse/HAWQ-1006
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Build, PXF
>Reporter: Goden Yao
>Assignee: Oleksandr Diachenko
> Fix For: 2.0.1.0-incubating
>
>
> Current Package name: apache-tomcat-7.0.62-.noarch
>  
> Installed Package Info:
> {code}
> [root@gbthadoop1x ~]# rpm -qi apache-tomcat.noarch
> Name: apache-tomcatRelocations: (not relocatable)
> Version : 7.0.62Vendor: Apache HAWQ Incubating
> Release :   Build Date: Thu 18 Feb 2016 
> 05:17:05 PM EST
> Install Date: Mon 08 Aug 2016 02:23:58 PM EDT  Build Host: shivram
> Group   : (none)   Source RPM: apache-tomcat-7.0.62--src.rpm
> Size: 13574438 License: ASL 2.0
> Signature   : (none)
> Packager: shivram
> URL :
> Summary : Apache Tomcat RPM
> Description :
> {code}
>  
> This is what an installed package from big-top tomcat.
> {code}
> Package Name: bigtop-tomcat-6.0.41-1.el6.noarch
>  
> Installed Package info:
> [root@gbthadoop1x ~]# rpm -qi bigtop-tomcat.noarch
> Name: bigtop-tomcatRelocations: (not relocatable)
> Version : 6.0.41Vendor: (none)
> Release : 1.el6 Build Date: Tue 31 Mar 2015 
> 05:17:15 PM EDT
> Install Date: Fri 15 Jul 2016 10:25:00 AM EDT  Build Host: 
> ip-10-0-0-90.ec2.internal
> Group   : Development/Libraries Source RPM: 
> bigtop-tomcat-6.0.41-1.el6.src.rpm
> Size: 6398489  License: ASL 2.0
> Signature   : RSA/SHA1, Tue 31 Mar 2015 07:14:29 PM EDT, Key ID 
> b9733a7a07513cad
> URL : http://tomcat.apache.org/
> Summary : Apache Tomcat
> Description :
> Apache Tomcat is an open source software implementation of the
> Java Servlet and JavaServer Pages technologies.
> {code}
> We need to remove individual info and add release info, group info and 
> description if missing
> **Other RPMs to fix**
> * pxf-hbase-3.0.0-22126.noarch.rpm - is the current one , .el6 missing at the 
> name of rpm
> * pxf-hdfs-3.0.0-22126.noarch.rpm - is the current one , .el6 missing at the 
> name of rpm
> * pxf-hive-3.0.0-22126.noarch.rpm - is the current one , .el6 missing at the 
> name of rpm
> * pxf-service-3.0.0-22126.noarch.rpm - is the current one , .el6 missing at 
> the name of rpm
> * pxf-json  (not released yet)



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

[jira] [Commented] (HAWQ-1031) updates docs to reflect MASTER_DATA_DIRECTORY code changes

[Lisa Owen (JIRA)]

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

Lisa Owen commented on HAWQ-1031:
-

HAWQ-1009 removed the requirements to set MASTER_DATA_DIRECTORY from 
gplogfilter (and maybe others).

> updates docs to reflect MASTER_DATA_DIRECTORY code changes
> --
>
> Key: HAWQ-1031
> URL: https://issues.apache.org/jira/browse/HAWQ-1031
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.0.1.0-incubating
>Reporter: Lisa Owen
>Assignee: Lei Chang
>Priority: Minor
> Fix For: 2.0.1.0-incubating
>
>
> MASTER_DATA_DIRECTORY is no longer a required environment variable for any 
> HAWQ command.  remove references in the docs, and point users to the 
> hawq-site.xml hawq_master_directory property value when required.



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

[GitHub] incubator-hawq pull request #873: HAWQ-992. PXF Hive data type check in Frag...

[sansanichfb]

GitHub user sansanichfb opened a pull request:

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

HAWQ-992. PXF Hive data type check in Fragmenter too restrictive.



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

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

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

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


commit 24f5e363d48f13108cb86750a5a5f2e76844a2f3
Author: Oleksandr Diachenko 
Date:   2016-08-24T23:54:55Z

HAWQ-992. PXF Hive data type check in Fragmenter too restrictive.

commit e2416f498ebb2be29712a1042c4e9bae99f523ff
Author: Oleksandr Diachenko 
Date:   2016-08-26T23:04:53Z

HAWQ-992. PXF Hive data type check in Fragmenter too restrictive.

commit 30aecce5aee1d45f9326618d255e64dbd2cdfdc5
Author: Oleksandr Diachenko 
Date:   2016-08-26T23:05:32Z

HAWQ-992. PXF Hive data type check in Fragmenter too restrictive.

commit 8b3f416eff5b48e3f41d4b969d7fbbb5a8c2a9ec
Author: Oleksandr Diachenko 
Date:   2016-08-27T00:20:38Z

HAWQ-992. PXF Hive data type check in Fragmenter too restrictive.




---
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-1031) updates docs to reflect MASTER_DATA_DIRECTORY code changes

[James Campbell (JIRA)]

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

James Campbell commented on HAWQ-1031:
--

gplogfilter uses the MASTER_DATA_DIRECTORY environment variable.  There may be 
other utilities that use it as well.

— 
Jim Campbell
jacampb...@pivotal.io 
O: 703-753-5970
M: 571-247-6511

On August 29, 2016 at 3:41:28 PM, Lisa Owen (JIRA) (j...@apache.org) wrote:

Lisa Owen created HAWQ-1031:  
---  

Summary: updates docs to reflect MASTER_DATA_DIRECTORY code changes  
Key: HAWQ-1031  
URL: https://issues.apache.org/jira/browse/HAWQ-1031  
Project: Apache HAWQ  
Issue Type: Bug  
Components: Documentation  
Reporter: Lisa Owen  
Assignee: Lei Chang  


MASTER_DATA_DIRECTORY is no longer a required environment variable for any HAWQ 
command. remove references in the docs, and point users to the hawq-site.xml 
hawq_master_directory property value when required.  



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


> updates docs to reflect MASTER_DATA_DIRECTORY code changes
> --
>
> Key: HAWQ-1031
> URL: https://issues.apache.org/jira/browse/HAWQ-1031
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.0.1.0-incubating
>Reporter: Lisa Owen
>Assignee: Lei Chang
>Priority: Minor
> Fix For: 2.0.1.0-incubating
>
>
> MASTER_DATA_DIRECTORY is no longer a required environment variable for any 
> HAWQ command.  remove references in the docs, and point users to the 
> hawq-site.xml hawq_master_directory property value when required.



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

[jira] [Updated] (HAWQ-1031) updates docs to reflect MASTER_DATA_DIRECTORY code changes

[Lisa Owen (JIRA)]

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

Lisa Owen updated HAWQ-1031:

Affects Version/s: 2.0.1.0-incubating

> updates docs to reflect MASTER_DATA_DIRECTORY code changes
> --
>
> Key: HAWQ-1031
> URL: https://issues.apache.org/jira/browse/HAWQ-1031
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.0.1.0-incubating
>Reporter: Lisa Owen
>Assignee: Lei Chang
>Priority: Minor
> Fix For: 2.0.1.0-incubating
>
>
> MASTER_DATA_DIRECTORY is no longer a required environment variable for any 
> HAWQ command.  remove references in the docs, and point users to the 
> hawq-site.xml hawq_master_directory property value when required.



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

[jira] [Updated] (HAWQ-1031) updates docs to reflect MASTER_DATA_DIRECTORY code changes

[Lisa Owen (JIRA)]

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

Lisa Owen updated HAWQ-1031:

Priority: Minor  (was: Major)

> updates docs to reflect MASTER_DATA_DIRECTORY code changes
> --
>
> Key: HAWQ-1031
> URL: https://issues.apache.org/jira/browse/HAWQ-1031
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.0.1.0-incubating
>Reporter: Lisa Owen
>Assignee: Lei Chang
>Priority: Minor
> Fix For: 2.0.1.0-incubating
>
>
> MASTER_DATA_DIRECTORY is no longer a required environment variable for any 
> HAWQ command.  remove references in the docs, and point users to the 
> hawq-site.xml hawq_master_directory property value when required.



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

[jira] [Updated] (HAWQ-1031) updates docs to reflect MASTER_DATA_DIRECTORY code changes

[Lisa Owen (JIRA)]

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

Lisa Owen updated HAWQ-1031:

Fix Version/s: 2.0.1.0-incubating

> updates docs to reflect MASTER_DATA_DIRECTORY code changes
> --
>
> Key: HAWQ-1031
> URL: https://issues.apache.org/jira/browse/HAWQ-1031
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.0.1.0-incubating
>Reporter: Lisa Owen
>Assignee: Lei Chang
>Priority: Minor
> Fix For: 2.0.1.0-incubating
>
>
> MASTER_DATA_DIRECTORY is no longer a required environment variable for any 
> HAWQ command.  remove references in the docs, and point users to the 
> hawq-site.xml hawq_master_directory property value when required.



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

[jira] [Created] (HAWQ-1031) updates docs to reflect MASTER_DATA_DIRECTORY code changes

[Lisa Owen (JIRA)]

Lisa Owen created HAWQ-1031:
---

 Summary: updates docs to reflect MASTER_DATA_DIRECTORY code changes
 Key: HAWQ-1031
 URL: https://issues.apache.org/jira/browse/HAWQ-1031
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Documentation
Reporter: Lisa Owen
Assignee: Lei Chang


MASTER_DATA_DIRECTORY is no longer a required environment variable for any HAWQ 
command.  remove references in the docs, and point users to the hawq-site.xml 
hawq_master_directory property value when required.



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

[jira] [Commented] (HAWQ-762) Hive aggregation queries through PXF sometimes hang

[Goden Yao (JIRA)]

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

Goden Yao commented on HAWQ-762:


I've got some other users reporting similar issues and will ask for logs to dig 
deeper.

> Hive aggregation queries through PXF sometimes hang
> ---
>
> Key: HAWQ-762
> URL: https://issues.apache.org/jira/browse/HAWQ-762
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Hcatalog, PXF
>Affects Versions: 2.0.0.0-incubating
>Reporter: Oleksandr Diachenko
>Assignee: Goden Yao
>  Labels: performance
> Fix For: backlog
>
>
> Reproduce Steps:
> {code}
> select count(*) from hcatalog.default.hivetable;
> {code}
> sometimes, this query will hang and we see from pxf logs that Hive thrift 
> server cannot be connected from PXF agent. 
> While users can still visit hive metastore (through HUE) and execute the same 
> query.
> After a restart of PXF agent, this query goes through without issues.
> *Troubleshooting Guide*
> - check catalina.out (tomcat) and pxf-service.log to see if the query request 
> gets to tomcat/pxf webapp, any exceptions happened during the time window
> - enable {code}log_min_messages=DEBUG2{code} to see at which step the query 
> is stuck
> - try:
> {code}
> curl http:///pxf/ProtocolVersion
> {code}
> where URI is the hostname or IP of the machine you installed PXF, port is 
> usually 51200 if you didn’t change it.
> The response you’ll get if PXF service is running OK:
> {code}
> {version: v14}
> {code}



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

[jira] [Updated] (HAWQ-1030) User hang due to poor spin-lock/LWLock performance under high concurrency

[Goden Yao (JIRA)]

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

Goden Yao updated HAWQ-1030:

Fix Version/s: 2.0.1.0-incubating

> User hang due to poor spin-lock/LWLock performance under high concurrency
> -
>
> Key: HAWQ-1030
> URL: https://issues.apache.org/jira/browse/HAWQ-1030
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Core
>Reporter: Ming LI
>Assignee: Ming LI
> Fix For: 2.0.1.0-incubating
>
>
> Some clients have recently reported apparent hangs with their applications. 
> In all cases the symptoms were the same:
> * All sessions appear to be hung in LWLockAcquire or Release, specifically 
> s_lock
> * there is a high number of concurrent sessions (close to 100)
> * System is not actually hung, normally processing resumes after some period 
> of time when all sessions have completed their locking work
> The postgresql developer community has found several issues with performance 
> under high concurrency (> 32 sessions) in the spin-lock mechanism we've 
> inherited in HAWQ. This ultimately has been corrected in 9.5 with a 
> replacement to the spin-lock mechanism and appears to provide a significant 
> boost to query performance.
> The actual fix is in commit: ab5194e6f617a9a9e7aadb3dd1cee948a42d0755
> Only 1 line commit to s_lock.c could help address this and would be easy 
> enough to cherry-pick: b03d196be055450c7260749f17347c2d066b4254



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

[jira] [Updated] (HAWQ-1027) Book configuration directory needs to be outside of content repo

[Goden Yao (JIRA)]

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

Goden Yao updated HAWQ-1027:

Fix Version/s: backlog

> Book configuration directory needs to be outside of content repo
> 
>
> Key: HAWQ-1027
> URL: https://issues.apache.org/jira/browse/HAWQ-1027
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: David Yozie
>Assignee: David Yozie
> Fix For: backlog
>
>
> The incubator-hawq-docs repo includes a sample book configuration (hawq-docs) 
> for producing HTML.  Unfortunately, this configuration directory causes 
> problems with the latest middleman that will be used in an upcoming 
> bookbinder release, so it needs to be moved.  
> We can probably get away with putting it in a separate branch for now.



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

[jira] [Updated] (HAWQ-1028) Add '-d' option for hawq state to be compatible with Ambari

[Goden Yao (JIRA)]

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

Goden Yao updated HAWQ-1028:

Fix Version/s: 2.0.1.0-incubating

> Add '-d' option for hawq state to be compatible with Ambari
> ---
>
> Key: HAWQ-1028
> URL: https://issues.apache.org/jira/browse/HAWQ-1028
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Command Line Tools
>Reporter: Radar Lei
>Assignee: Radar Lei
> Fix For: 2.0.1.0-incubating
>
>
> Previously we removed the legacy option '-d' '--datadir' from 'hawq state' 
> command. This option is used to specify the master data directory, but we 
> never used it in our command line tools.
> Now we found this unused option is used by current version Ambari, and will 
> cause Ambari check HAWQ status failed if we removed it. So to be compatible 
> with Ambari, we need to add it back until Ambari do not use this option.



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

[jira] [Resolved] (HAWQ-1013) Move HAWQ Ambari plugin to Apache HAWQ

[Matt (JIRA)]

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

Matt resolved HAWQ-1013.

Resolution: Done

> Move HAWQ Ambari plugin to Apache HAWQ
> --
>
> Key: HAWQ-1013
> URL: https://issues.apache.org/jira/browse/HAWQ-1013
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Ambari
>Reporter: Matt
>Assignee: Alexander Denissov
>  Labels: UX
> Fix For: backlog
>
>
> To add HAWQ and PXF to Ambari, users have to follow certain manual steps. 
> These manual steps include:
> - Adding HAWQ and PXF metainfo.xml files (containing metadata about the 
> service) under the stack to be installed.
> - Adding repositories, where HAWQ and PXF rpms reside so that Ambari can use 
> it during installation. This requires updating repoinfo.xml under the stack 
> HAWQ and PXF is being added to.
> - Adding repositories to an existing stack managed by Ambari requires adding 
> the repositories using the Ambari REST endpoint.
> The HAWQ Ambari plugin automates the above steps using a script.



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

[jira] [Assigned] (HAWQ-986) Redundant Fragmenter API Call from Reading External Table

[Kavinder Dhaliwal (JIRA)]

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

Kavinder Dhaliwal reassigned HAWQ-986:
--

Assignee: Kavinder Dhaliwal  (was: Goden Yao)

> Redundant Fragmenter API Call from Reading External Table
> -
>
> Key: HAWQ-986
> URL: https://issues.apache.org/jira/browse/HAWQ-986
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Oleksandr Diachenko
>Assignee: Kavinder Dhaliwal
> Fix For: backlog
>
>
> Right now, when HAWQ does select from external PXF table it does two 
> fragmenter calls, seems like it's redundant.



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

[jira] [Resolved] (HAWQ-986) Redundant Fragmenter API Call from Reading External Table

[Kavinder Dhaliwal (JIRA)]

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

Kavinder Dhaliwal resolved HAWQ-986.

Resolution: Not A Problem

> Redundant Fragmenter API Call from Reading External Table
> -
>
> Key: HAWQ-986
> URL: https://issues.apache.org/jira/browse/HAWQ-986
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Oleksandr Diachenko
>Assignee: Kavinder Dhaliwal
> Fix For: backlog
>
>
> Right now, when HAWQ does select from external PXF table it does two 
> fragmenter calls, seems like it's redundant.



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

[jira] [Commented] (HAWQ-986) Redundant Fragmenter API Call from Reading External Table

[Kavinder Dhaliwal (JIRA)]

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

Kavinder Dhaliwal commented on HAWQ-986:


This is a known design decision. HAWQ calls the planner twice in order to do 
dynamic resource negotiation with every query.

> Redundant Fragmenter API Call from Reading External Table
> -
>
> Key: HAWQ-986
> URL: https://issues.apache.org/jira/browse/HAWQ-986
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Oleksandr Diachenko
>Assignee: Goden Yao
> Fix For: backlog
>
>
> Right now, when HAWQ does select from external PXF table it does two 
> fragmenter calls, seems like it's redundant.



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

[jira] [Resolved] (HAWQ-1019) clarify database application interfaces discussion

[Lisa Owen (JIRA)]

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

Lisa Owen resolved HAWQ-1019.
-
Resolution: Fixed

> clarify database application interfaces discussion
> --
>
> Key: HAWQ-1019
> URL: https://issues.apache.org/jira/browse/HAWQ-1019
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Lisa Owen
>Assignee: Lei Chang
>Priority: Minor
> Fix For: 2.0.1.0-incubating
>
>
> discussion of drivers for database application interfaces needs to be 
> clarified.
> relevant incubator-hawq-docs file:  
> clientaccess/g-database-application-interfaces.html.md.erb 



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

[GitHub] incubator-hawq issue #872: HAWQ-1030. Forward PostgreSQL spin lock peformanc...

[paul-guo-]

Github user paul-guo- commented on the issue:

https://github.com/apache/incubator-hawq/pull/872
  
The patch is beneficial generally. hawq should include it.

I'm just curious about the upstream implementation of spin lock. This is a 
bit not related to this patch, but I'd express my option here.

1) pg_usleep() uses the select() way.

Not sure whether the comment still applies to some latest HW and SW, but
isn't a posix delay syscall nanosleep(), which is with high resoluation 
better?

+/*
+ * pg_usleep --- delay the specified number of microseconds.
+ *
+ * NOTE: although the delay is specified in microseconds, the effective
+ * resolution is only 1/HZ, or 10 milliseconds, on most Unixen.  Expect
+ * the requested delay to be rounded up to the next resolution boundary.
+ *
+ * On machines where "long" is 32 bits, the maximum delay is ~2000 seconds.
+ */
+void
+pg_usleep(long microsec)
+{
+   if (microsec > 0)
+   {
+#ifndef WIN32
+   struct timeval delay;
+
+   delay.tv_sec = microsec / 100L;
+   delay.tv_usec = microsec % 100L;
+   (void) select(0, NULL, NULL, NULL, );
+#else

2) spin lock is used for cases that the resource will be released soon, so 
I guess a sched_yield() after some backoff pause is probably more suitable for 
spinlock (probably could be combined with some process priority adjustment) 
since it will reduce the latency, even with some additional cpu cost. If there 
are cases that could lock for a bit longer, a blocking lock should be 
implemented/used instead.



---
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 #872: HAWQ-1030. Forward PostgreSQL spin lock pe...

[liming01]

GitHub user liming01 opened a pull request:

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

HAWQ-1030. Forward PostgreSQL spin lock peformance enhancement to HAWQ

Hawq didn't change the implementation of spin lock which is same with 
postgresql, thinking that porting from new version of postgresql in the future, 
here we keep the code more similar to latest postgresql.


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

$ git pull https://github.com/liming01/incubator-hawq mli/spinlock_perf

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

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


commit 3e849910eb6ce27d183348c4fd60fcbaf71cd1dd
Author: Ming LI 
Date:   2016-08-29T08:42:33Z

HAWQ-1030. Forward PostgreSQL spin lock peformance enhancement to HAWQ




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

[jira] [Assigned] (HAWQ-1030) User hang due to poor spin-lock/LWLock performance under high concurrency

[Ming LI (JIRA)]

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

Ming LI reassigned HAWQ-1030:
-

Assignee: Ming LI  (was: Lei Chang)

> User hang due to poor spin-lock/LWLock performance under high concurrency
> -
>
> Key: HAWQ-1030
> URL: https://issues.apache.org/jira/browse/HAWQ-1030
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Core
>Reporter: Ming LI
>Assignee: Ming LI
>
> Some clients have recently reported apparent hangs with their applications. 
> In all cases the symptoms were the same:
> * All sessions appear to be hung in LWLockAcquire or Release, specifically 
> s_lock
> * there is a high number of concurrent sessions (close to 100)
> * System is not actually hung, normally processing resumes after some period 
> of time when all sessions have completed their locking work
> The postgresql developer community has found several issues with performance 
> under high concurrency (> 32 sessions) in the spin-lock mechanism we've 
> inherited in HAWQ. This ultimately has been corrected in 9.5 with a 
> replacement to the spin-lock mechanism and appears to provide a significant 
> boost to query performance.
> The actual fix is in commit: ab5194e6f617a9a9e7aadb3dd1cee948a42d0755
> Only 1 line commit to s_lock.c could help address this and would be easy 
> enough to cherry-pick: b03d196be055450c7260749f17347c2d066b4254



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

[jira] [Created] (HAWQ-1030) User hang due to poor spin-lock/LWLock performance under high concurrency

[Ming LI (JIRA)]

Ming LI created HAWQ-1030:
-

 Summary: User hang due to poor spin-lock/LWLock performance under 
high concurrency
 Key: HAWQ-1030
 URL: https://issues.apache.org/jira/browse/HAWQ-1030
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Core
Reporter: Ming LI
Assignee: Lei Chang


Some clients have recently reported apparent hangs with their applications. In 
all cases the symptoms were the same:

* All sessions appear to be hung in LWLockAcquire or Release, specifically 
s_lock
* there is a high number of concurrent sessions (close to 100)
* System is not actually hung, normally processing resumes after some period of 
time when all sessions have completed their locking work

The postgresql developer community has found several issues with performance 
under high concurrency (> 32 sessions) in the spin-lock mechanism we've 
inherited in HAWQ. This ultimately has been corrected in 9.5 with a replacement 
to the spin-lock mechanism and appears to provide a significant boost to query 
performance.

The actual fix is in commit: ab5194e6f617a9a9e7aadb3dd1cee948a42d0755

Only 1 line commit to s_lock.c could help address this and would be easy enough 
to cherry-pick: b03d196be055450c7260749f17347c2d066b4254



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

[jira] [Updated] (HAWQ-256) Integrate Security with Apache Ranger

[Lili Ma (JIRA)]

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

Lili Ma updated HAWQ-256:
-
Attachment: (was: HAWQRangerSupportDesign_v0.2.pdf)

> Integrate Security with Apache Ranger
> -
>
> Key: HAWQ-256
> URL: https://issues.apache.org/jira/browse/HAWQ-256
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF, Security
>Reporter: Michael Andre Pearce (IG)
>Assignee: Lili Ma
> Fix For: backlog
>
> Attachments: HAWQRangerSupportDesign.pdf, 
> HAWQRangerSupportDesign_v0.2.pdf
>
>
> Integrate security with Apache Ranger for a unified Hadoop security solution. 



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

[jira] [Updated] (HAWQ-256) Integrate Security with Apache Ranger

[Lili Ma (JIRA)]

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

Lili Ma updated HAWQ-256:
-
Attachment: HAWQRangerSupportDesign_v0.2.pdf

> Integrate Security with Apache Ranger
> -
>
> Key: HAWQ-256
> URL: https://issues.apache.org/jira/browse/HAWQ-256
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF, Security
>Reporter: Michael Andre Pearce (IG)
>Assignee: Lili Ma
> Fix For: backlog
>
> Attachments: HAWQRangerSupportDesign.pdf, 
> HAWQRangerSupportDesign_v0.2.pdf
>
>
> Integrate security with Apache Ranger for a unified Hadoop security solution. 



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

[jira] [Updated] (HAWQ-256) Integrate Security with Apache Ranger

[Lili Ma (JIRA)]

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

Lili Ma updated HAWQ-256:
-
Attachment: HAWQRangerSupportDesign_v0.2.pdf

Attach a new version of design doc for HAWQ Ranger Integration, mainly 
checkPrivilege change. Thanks

> Integrate Security with Apache Ranger
> -
>
> Key: HAWQ-256
> URL: https://issues.apache.org/jira/browse/HAWQ-256
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF, Security
>Reporter: Michael Andre Pearce (IG)
>Assignee: Lili Ma
> Fix For: backlog
>
> Attachments: HAWQRangerSupportDesign.pdf, 
> HAWQRangerSupportDesign_v0.2.pdf
>
>
> Integrate security with Apache Ranger for a unified Hadoop security solution. 



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

[jira] [Closed] (HAWQ-1021) Need to log for some local_ssh function calls.

[Paul Guo (JIRA)]

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

Paul Guo closed HAWQ-1021.
--
Resolution: Fixed
  Assignee: Paul Guo  (was: hongwu)

> Need to log for some local_ssh function calls.
> --
>
> Key: HAWQ-1021
> URL: https://issues.apache.org/jira/browse/HAWQ-1021
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Paul Guo
>Assignee: Paul Guo
> Fix For: 2.0.1.0-incubating
>
>
> HAWQ management tools calls a lot of local_ssh() function to run some 
> external commands. The function is defined in hawqpylib/hawqlib.py. Many 
> callers does not set logger so we do not know any details about the command 
> running process. This is annoying when users/developers fail to run some 
> related commands and want to know the root cause quickly.
> Besides, there is two definitions of local_ssh(). Although they are not in 
> the same namespace, it is kind of annoying. We need to rename either one or 
> even both.



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