[jira] [Updated] (HAWQ-845) Parameter kerberos principal name for HAWQ

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated HAWQ-845:

Description: 
Currently HAWQ only accept the principle 'postgres' for kerberos settings.
This is because there its hardcoded in gpcheckhdfs, we should ensure that it 
can be parameterized.

Also, its better to change the default principal name postgres to gpadmin. It 
will avoid the need of changing the the hdfs directory during securing the 
cluster to postgres and will avoid the need of maintaing postgres user. 

  was:
Currently HAWQ only accept the principle 'postgres' for kerberos settings.
This is because there its hardcoded in gpcheckhdfs, we should ensure that it 
can be parameterized.


> Parameter kerberos principal name for HAWQ
> --
>
> Key: HAWQ-845
> URL: https://issues.apache.org/jira/browse/HAWQ-845
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: bhuvnesh chaudhary
>Assignee: Lei Chang
>
> Currently HAWQ only accept the principle 'postgres' for kerberos settings.
> This is because there its hardcoded in gpcheckhdfs, we should ensure that it 
> can be parameterized.
> Also, its better to change the default principal name postgres to gpadmin. It 
> will avoid the need of changing the the hdfs directory during securing the 
> cluster to postgres and will avoid the need of maintaing postgres user. 



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

[jira] [Created] (HAWQ-845) Parameter kerberos principal name for HAWQ

[bhuvnesh chaudhary (JIRA)]

bhuvnesh chaudhary created HAWQ-845:
---

 Summary: Parameter kerberos principal name for HAWQ
 Key: HAWQ-845
 URL: https://issues.apache.org/jira/browse/HAWQ-845
 Project: Apache HAWQ
  Issue Type: Bug
Reporter: bhuvnesh chaudhary
Assignee: Lei Chang


Currently HAWQ only accept the principle 'postgres' for kerberos settings.
This is because there its hardcoded in gpcheckhdfs, we should ensure that it 
can be parameterized.



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

[jira] [Comment Edited] (HAWQ-844) Please remove your private branch from apache hawq project on githup

[Ming LI (JIRA)]

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

Ming LI edited comment on HAWQ-844 at 6/21/16 5:31 AM:
---

Hi [~bhuvnesh2703] 
[~shivram]
[~c0stra], 

FYI.


was (Author: mli):
Hi [~bhuvnesh2703] [~shivram][~c0stra], FYI.

> Please remove your private branch from apache hawq project on githup
> 
>
> Key: HAWQ-844
> URL: https://issues.apache.org/jira/browse/HAWQ-844
> Project: Apache HAWQ
>  Issue Type: Task
>Reporter: Ming LI
>Assignee: Lei Chang
>
> We are planning the new release on apache hawq, it is better to keep the git 
> branch list clean, however there are a lot private branch on 
> https://github.com/apache/incubator-hawq/branches, which make user/developer 
> confusing. 
> Could you please remove those private branch from the public hawq repo?  I 
> don't know who have privilege to remove it, maybe the branch owner can have.
> FYI, All developer who want to checkin your code change, the better way is as 
> below: 
> 1) Login your githup account, and clone hawq repo to your private repo. 
> 2) Create a git branch locally, commit your code changes in this new branch
> 3) Push this new branch to your private repo on githup
> 4) Go to  https://github.com/apache/incubator-hawq to create pull request.



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

[jira] [Commented] (HAWQ-844) Please remove your private branch from apache hawq project on githup

[Ming LI (JIRA)]

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

Ming LI commented on HAWQ-844:
--

Hi [~bhuvnesh2703] [~shivram][~c0stra], FYI.

> Please remove your private branch from apache hawq project on githup
> 
>
> Key: HAWQ-844
> URL: https://issues.apache.org/jira/browse/HAWQ-844
> Project: Apache HAWQ
>  Issue Type: Task
>Reporter: Ming LI
>Assignee: Lei Chang
>
> We are planning the new release on apache hawq, it is better to keep the git 
> branch list clean, however there are a lot private branch on 
> https://github.com/apache/incubator-hawq/branches, which make user/developer 
> confusing. 
> Could you please remove those private branch from the public hawq repo?  I 
> don't know who have privilege to remove it, maybe the branch owner can have.
> FYI, All developer who want to checkin your code change, the better way is as 
> below: 
> 1) Login your githup account, and clone hawq repo to your private repo. 
> 2) Create a git branch locally, commit your code changes in this new branch
> 3) Push this new branch to your private repo on githup
> 4) Go to  https://github.com/apache/incubator-hawq to create pull request.



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

[jira] [Created] (HAWQ-844) Please remove your private branch from apache hawq project on githup

[Ming LI (JIRA)]

Ming LI created HAWQ-844:


 Summary: Please remove your private branch from apache hawq 
project on githup
 Key: HAWQ-844
 URL: https://issues.apache.org/jira/browse/HAWQ-844
 Project: Apache HAWQ
  Issue Type: Task
Reporter: Ming LI
Assignee: Lei Chang


We are planning the new release on apache hawq, it is better to keep the git 
branch list clean, however there are a lot private branch on 
https://github.com/apache/incubator-hawq/branches, which make user/developer 
confusing. 

Could you please remove those private branch from the public hawq repo?  I 
don't know who have privilege to remove it, maybe the branch owner can have.

FYI, All developer who want to checkin your code change, the better way is as 
below: 
1) Login your githup account, and clone hawq repo to your private repo. 
2) Create a git branch locally, commit your code changes in this new branch
3) Push this new branch to your private repo on githup
4) Go to  https://github.com/apache/incubator-hawq to create pull request.





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

[jira] [Commented] (HAWQ-823) Amazon S3 External Table Support

[Lei Chang (JIRA)]

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

Lei Chang commented on HAWQ-823:


the hawq architecture for supporting this feature will be somewhat different 
from gpdb. And the new framework to support pluggable file system has been 
proposed here: https://issues.apache.org/jira/browse/HAWQ-786 so we can see we 
can combine the work together.

> Amazon S3 External Table Support
> 
>
> Key: HAWQ-823
> URL: https://issues.apache.org/jira/browse/HAWQ-823
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: External Tables
>Reporter: Kyle R Dunn
>Assignee: Lei Chang
>
> As a cloud user, I'd like to be able to create readable external tables with 
> data in Amazon S3.



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

[jira] [Closed] (HAWQ-833) Lack of pgcrypto.sql for the pgcrypto support

[Paul Guo (JIRA)]

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

Paul Guo closed HAWQ-833.
-
Resolution: Fixed
  Assignee: Paul Guo  (was: Lei Chang)

> Lack of pgcrypto.sql for the pgcrypto support
> -
>
> Key: HAWQ-833
> URL: https://issues.apache.org/jira/browse/HAWQ-833
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Paul Guo
>Assignee: Paul Guo
>
> Currently we use upstream postgres/pgcrypto for the pgcrypto support. The 
> version we are using just provides the sql file for the "create extension" 
> command which has not been supported on our code. We need to provide a 
> separate  pgcrypto.sql (and its corresponding uninstall sql file), just like 
> what pl/plr code does, then users could use the pgcrypto functionality as 
> before.



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

[jira] [Closed] (HAWQ-841) Running "make -j8 unittest-check" under src/backend will throw "File exists" error

[Paul Guo (JIRA)]

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

Paul Guo closed HAWQ-841.
-
Resolution: Fixed
  Assignee: Paul Guo  (was: Jiali Yao)

> Running "make -j8 unittest-check" under src/backend will throw "File exists" 
> error
> --
>
> Key: HAWQ-841
> URL: https://issues.apache.org/jira/browse/HAWQ-841
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Tests
>Reporter: Paul Guo
>Assignee: Paul Guo
>
> ERROR:root:Error has occurred during parsing 
> /home/build/incubator-hawq/src/backend/executor/execAmi.c: [Errno 17] File 
> exists: '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> Traceback (most recent call last):
>   File "mocker.py", line 307, in 
> main()
>   File "mocker.py", line 300, in main
> mock = MockFile(cfile, options)
>   File "mocker.py", line 121, in __init__
> self.outname = self.output_filename()
>   File "mocker.py", line 132, in output_filename
> os.makedirs(out_dir)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 17] File exists: 
> '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> mocking /home/build/incubator-hawq/src/backend/executor/execQual.c
> make[4]: *** 
> [../../../../../src/test/unit/mock/backend/executor/execAmi_mock.c] Error 1
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[3]: *** [mockup-phony] Error 2
> make[3]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[2]: *** [unittest-check] Error 2
> make[2]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common'
> make[1]: *** [unittest-check] Error 2
> make[1]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access'
> make: *** [unittest-check] Error 2



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

[jira] [Commented] (HAWQ-841) Running "make -j8 unittest-check" under src/backend will throw "File exists" error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-841:
-

Github user paul-guo- closed the pull request at:

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


> Running "make -j8 unittest-check" under src/backend will throw "File exists" 
> error
> --
>
> Key: HAWQ-841
> URL: https://issues.apache.org/jira/browse/HAWQ-841
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Tests
>Reporter: Paul Guo
>Assignee: Jiali Yao
>
> ERROR:root:Error has occurred during parsing 
> /home/build/incubator-hawq/src/backend/executor/execAmi.c: [Errno 17] File 
> exists: '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> Traceback (most recent call last):
>   File "mocker.py", line 307, in 
> main()
>   File "mocker.py", line 300, in main
> mock = MockFile(cfile, options)
>   File "mocker.py", line 121, in __init__
> self.outname = self.output_filename()
>   File "mocker.py", line 132, in output_filename
> os.makedirs(out_dir)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 17] File exists: 
> '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> mocking /home/build/incubator-hawq/src/backend/executor/execQual.c
> make[4]: *** 
> [../../../../../src/test/unit/mock/backend/executor/execAmi_mock.c] Error 1
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[3]: *** [mockup-phony] Error 2
> make[3]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[2]: *** [unittest-check] Error 2
> make[2]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common'
> make[1]: *** [unittest-check] Error 2
> make[1]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access'
> make: *** [unittest-check] Error 2



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

[jira] [Commented] (HAWQ-841) Running "make -j8 unittest-check" under src/backend will throw "File exists" error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-841:
-

Github user paul-guo- commented on the issue:

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


> Running "make -j8 unittest-check" under src/backend will throw "File exists" 
> error
> --
>
> Key: HAWQ-841
> URL: https://issues.apache.org/jira/browse/HAWQ-841
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Tests
>Reporter: Paul Guo
>Assignee: Jiali Yao
>
> ERROR:root:Error has occurred during parsing 
> /home/build/incubator-hawq/src/backend/executor/execAmi.c: [Errno 17] File 
> exists: '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> Traceback (most recent call last):
>   File "mocker.py", line 307, in 
> main()
>   File "mocker.py", line 300, in main
> mock = MockFile(cfile, options)
>   File "mocker.py", line 121, in __init__
> self.outname = self.output_filename()
>   File "mocker.py", line 132, in output_filename
> os.makedirs(out_dir)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 17] File exists: 
> '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> mocking /home/build/incubator-hawq/src/backend/executor/execQual.c
> make[4]: *** 
> [../../../../../src/test/unit/mock/backend/executor/execAmi_mock.c] Error 1
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[3]: *** [mockup-phony] Error 2
> make[3]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[2]: *** [unittest-check] Error 2
> make[2]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common'
> make[1]: *** [unittest-check] Error 2
> make[1]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access'
> make: *** [unittest-check] Error 2



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

[GitHub] incubator-hawq pull request #732: HAWQ-833. Lack of pgcrypto.sql for the pgc...

[paul-guo-]

Github user paul-guo- closed the pull request at:

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


---
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 #734: HAWQ-841. Running "make -j8 unittest-check" under...

[paul-guo-]

Github user paul-guo- commented on the issue:

https://github.com/apache/incubator-hawq/pull/734
  
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] [Created] (HAWQ-843) HAWQ 2.0 new error handling mechanism implementation

[Lili Ma (JIRA)]

Lili Ma created HAWQ-843:


 Summary: HAWQ 2.0 new error handling mechanism implementation
 Key: HAWQ-843
 URL: https://issues.apache.org/jira/browse/HAWQ-843
 Project: Apache HAWQ
  Issue Type: Wish
Reporter: Lili Ma
Assignee: Lei Chang


As a HAWQ user, I want other QEs of the same query still keep alive when one QE 
fails, so that I can reuse the alive QEs to execute the following queries.



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

[jira] [Commented] (HAWQ-837) Add python modules into HAWQ code except paramiko

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-837:
-

Github user asfgit closed the pull request at:

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


> Add python modules into HAWQ code except paramiko
> -
>
> Key: HAWQ-837
> URL: https://issues.apache.org/jira/browse/HAWQ-837
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Build
>Reporter: Radar Lei
>Assignee: Lei Chang
>
> Add below python modules which compatible with Apache HAWQ license. Paramiko 
> won't be added.
> figleaf   BSD
> pg8000BSD
> pygresql  Python
> simplejsonMIT
> pyyamlMIT
> lockfile  OSI Approved :: MIT License
> psi   MIT
> pychecker BSD-like
> unittest2 OSI Approved :: BSD License
> pycrypto  Public domain



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

[GitHub] incubator-hawq pull request #735: HAWQ-837. Add python modules into HAWQ cod...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-837) Add python modules into HAWQ code except paramiko

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-837:
-

Github user yaoj2 commented on the issue:

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


> Add python modules into HAWQ code except paramiko
> -
>
> Key: HAWQ-837
> URL: https://issues.apache.org/jira/browse/HAWQ-837
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Build
>Reporter: Radar Lei
>Assignee: Lei Chang
>
> Add below python modules which compatible with Apache HAWQ license. Paramiko 
> won't be added.
> figleaf   BSD
> pg8000BSD
> pygresql  Python
> simplejsonMIT
> pyyamlMIT
> lockfile  OSI Approved :: MIT License
> psi   MIT
> pychecker BSD-like
> unittest2 OSI Approved :: BSD License
> pycrypto  Public domain



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

[jira] [Commented] (HAWQ-837) Add python modules into HAWQ code except paramiko

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-837:
-

Github user huor commented on the issue:

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


> Add python modules into HAWQ code except paramiko
> -
>
> Key: HAWQ-837
> URL: https://issues.apache.org/jira/browse/HAWQ-837
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Build
>Reporter: Radar Lei
>Assignee: Lei Chang
>
> Add below python modules which compatible with Apache HAWQ license. Paramiko 
> won't be added.
> figleaf   BSD
> pg8000BSD
> pygresql  Python
> simplejsonMIT
> pyyamlMIT
> lockfile  OSI Approved :: MIT License
> psi   MIT
> pychecker BSD-like
> unittest2 OSI Approved :: BSD License
> pycrypto  Public domain



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

[GitHub] incubator-hawq issue #735: HAWQ-837. Add python modules into HAWQ code

[huor]

Github user huor commented on the issue:

https://github.com/apache/incubator-hawq/pull/735
  
+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] [Updated] (HAWQ-842) Failed to acquire resource from resource manager

[Bill Wailliam (JIRA)]

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

Bill Wailliam updated HAWQ-842:
---
Description: 
This is the pg_log:
2016-06-20 17:56:03.864644 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","database system 
was shut down at 2016-06-20 17:54:32 CST",,,0,,"xlog.c",6205,
2016-06-20 17:56:03.864908 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","checkpoint record 
is at 0/2672EF8",,,0,,"xlog.c",6304,
2016-06-20 17:56:03.864923 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","redo record is at 
0/2672EF8; undo record is at 0/0; shutdown TRUE",,,0,,"xlog.c",6338,
2016-06-20 17:56:03.864933 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","next transaction 
ID: 0/1284; next OID: 16514",,,0,,"xlog.c",6342,
2016-06-20 17:56:03.864942 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","next MultiXactId: 
1; next MultiXactOffset: 0",,,0,,"xlog.c",6345,
2016-06-20 17:56:03.864951 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","end of 
transaction log location is 0/2672F48",,,0,,"xlog.c",6582,
2016-06-20 17:56:03.865750 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","Oldest active 
transaction from prepared transactions 1284",,,0,,"xlog.c",5996,
2016-06-20 17:56:03.867372 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","database system 
is ready",,,0,,"xlog.c",6022,
2016-06-20 17:56:03.867394 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","PostgreSQL 8.2.15 
(Greenplum Database 4.2.0 build 1) (HAWQ 2.0.0.0 build dev) on 
x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.8.0 compiled on Jun 19 
2016 03:02:01",,,0,,"xlog.c",6032,
2016-06-20 17:56:03.868503 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","Finished normal 
startup for clean shutdown case",,,0,,"xlog.c",6810,
2016-06-20 17:56:03.876213 
CST,,,p526097,th5032941760,,,seg-1,"LOG","0","Finished startup 
integrity checking",,,0,,"xlog.c",7159,
2016-06-20 17:56:03.879998 
CST,,,p526104,th5032941760,,,seg-1,"LOG","0","HAWQ Segment RM 
:: Temporary directory /data1/hawq/tmp",,,0,,"resourcemanager.c",1055,
2016-06-20 17:56:03.880039 
CST,,,p526104,th5032941760,,,seg-1,"LOG","0","checkAndBuildFailedTmpDirList
 finished checking temporary directory, which costs 41 
us",,,0,,"resourcemanager_RMSEG.c",274,
2016-06-20 17:56:03.883958 
CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","YARN mode 
resource broker created resource broker process 
PID=526105.",,,0,,"resourcebroker_LIBYARN.c",158,
2016-06-20 17:56:03.884155 
CST,,,p526105,th5032941760,con4,,seg-1,"LOG","0","YARN mode 
resource broker accepted YARN connection arguments : YARN Server 
RM_IP_XX:8032 Scheduler server RM_IP_XX:8030 Queue hawq Application 
name hawq, by user:postgres",,,0,,"resourcebroker_LIBYARN_proc.c",501,
2016-06-20 17:56:03.884283 
CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","Resource 
manager starts accepting resource request. Listening normal socket port 5437. 
Total listened 1 FDs.",,,0,,"resourcemanager.c",2492,
2016-06-20 17:56:03.884378 
CST,,,p526094,th5032941760,,,seg-1,"LOG","0","Wait for HAWQ RM 
-1",,,0,,"resourcemanager.c",421,
2016-06-20 17:56:03.884409 
CST,,,p526094,th5032941760,,,seg-1,"LOG","0","HAWQ :: Received 
signal notification that HAWQ RM works now.",,,0,,"resourcemanager.c",429,
2016-06-20 17:56:03.884424 
CST,,,p526094,th5032941760,,,seg-1,"LOG","0","PostgreSQL 8.2.15 
(Greenplum Database 4.2.0 build 1) (HAWQ 2.0.0.0 build dev) on 
x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.8.0 compiled on Jun 19 
2016 03:02:03",,,0,,"postmaster.c",3694,
2016-06-20 17:56:03.884441 
CST,,,p526094,th5032941760,,,seg-1,"LOG","0","database system 
is ready to accept connections","PostgreSQL 8.2.15 (Greenplum Database 4.2.0 
build 1) (HAWQ 2.0.0.0 build dev) on x86_64-unknown-linux-gnu, compiled by GCC 
gcc (GCC) 4.8.0 compiled on Jun 19 2016 03:02:03",,0,,"postmaster.c",3701,
2016-06-20 17:56:03.885673 
CST,,,p526095,th5032941760,,,seg-1,"LOG","0","3rd party error 
log:
2016-06-20 17:56:03.885486, p526105, th140510358382816, INFO ApplicationClient 
session auth method : simple""SysLoggerMain","syslogger.c",518,
2016-06-20 17:56:03.892215 
CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","Cleanup 
segment configuration catalog table 
successfully!",,,0,,"resourcepool.c",460,
2016-06-20 17:56:03.892604 
CST,,,p526095,th5032941760,,,seg-1,"LOG","0","3rd party error 
log:
2016-06-20 17:56:03.892561, p526105, th140510358382816, INFO Yarn RM HA is not 
configured.""SysLoggerMain","syslogger.c",518,
2016-06-20 

[jira] [Commented] (HAWQ-842) Failed to acquire resource from resource manager

[Bill Wailliam (JIRA)]

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

Bill Wailliam commented on HAWQ-842:


HAWQ version is 2.0.0.0 build dev from github master.The latest submission is 
is 583ef22e0da0522fe13ad6b1fc1188fc2abca1c4
Hadoop version info:
  Hadoop 2.7.1
  Compiled by hadoop on 2016-02-26T10:33Z
  Compiled with protoc 2.5.0

When the cluster starts from pg_log can see the error.

> Failed to acquire resource from resource manager
> 
>
> Key: HAWQ-842
> URL: https://issues.apache.org/jira/browse/HAWQ-842
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Bill Wailliam
>Assignee: Lei Chang
>
> This is the pg_log:
> 2016-06-20 17:56:03.864644 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","database system 
> was shut down at 2016-06-20 17:54:32 CST",,,0,,"xlog.c",6205,
> 2016-06-20 17:56:03.864908 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","checkpoint 
> record is at 0/2672EF8",,,0,,"xlog.c",6304,
> 2016-06-20 17:56:03.864923 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","redo record is 
> at 0/2672EF8; undo record is at 0/0; shutdown TRUE",,,0,,"xlog.c",6338,
> 2016-06-20 17:56:03.864933 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","next 
> transaction ID: 0/1284; next OID: 16514",,,0,,"xlog.c",6342,
> 2016-06-20 17:56:03.864942 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","next 
> MultiXactId: 1; next MultiXactOffset: 0",,,0,,"xlog.c",6345,
> 2016-06-20 17:56:03.864951 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","end of 
> transaction log location is 0/2672F48",,,0,,"xlog.c",6582,
> 2016-06-20 17:56:03.865750 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","Oldest active 
> transaction from prepared transactions 1284",,,0,,"xlog.c",5996,
> 2016-06-20 17:56:03.867372 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","database system 
> is ready",,,0,,"xlog.c",6022,
> 2016-06-20 17:56:03.867394 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","PostgreSQL 
> 8.2.15 (Greenplum Database 4.2.0 build 1) (HAWQ 2.0.0.0 build dev) on 
> x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.8.0 compiled on Jun 19 
> 2016 03:02:01",,,0,,"xlog.c",6032,
> 2016-06-20 17:56:03.868503 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","Finished normal 
> startup for clean shutdown case",,,0,,"xlog.c",6810,
> 2016-06-20 17:56:03.876213 
> CST,,,p526097,th5032941760,,,seg-1,"LOG","0","Finished 
> startup integrity checking",,,0,,"xlog.c",7159,
> 2016-06-20 17:56:03.879998 
> CST,,,p526104,th5032941760,,,seg-1,"LOG","0","HAWQ Segment RM 
> :: Temporary directory /data1/hawq/tmp",,,0,,"resourcemanager.c",1055,
> 2016-06-20 17:56:03.880039 
> CST,,,p526104,th5032941760,,,seg-1,"LOG","0","checkAndBuildFailedTmpDirList
>  finished checking temporary directory, which costs 41 
> us",,,0,,"resourcemanager_RMSEG.c",274,
> 2016-06-20 17:56:03.883958 
> CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","YARN mode 
> resource broker created resource broker process 
> PID=526105.",,,0,,"resourcebroker_LIBYARN.c",158,
> 2016-06-20 17:56:03.884155 
> CST,,,p526105,th5032941760,con4,,seg-1,"LOG","0","YARN mode 
> resource broker accepted YARN connection arguments : YARN Server 
> RM_IP_XX:8032 Scheduler server RM_IP_XX:8030 Queue hawq Application 
> name hawq, by user:postgres",,,0,,"resourcebroker_LIBYARN_proc.c",501,
> 2016-06-20 17:56:03.884283 
> CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","Resource 
> manager starts accepting resource request. Listening normal socket port 5437. 
> Total listened 1 FDs.",,,0,,"resourcemanager.c",2492,
> 2016-06-20 17:56:03.884378 
> CST,,,p526094,th5032941760,,,seg-1,"LOG","0","Wait for HAWQ 
> RM -1",,,0,,"resourcemanager.c",421,
> 2016-06-20 17:56:03.884409 
> CST,,,p526094,th5032941760,,,seg-1,"LOG","0","HAWQ :: 
> Received signal notification that HAWQ RM works 
> now.",,,0,,"resourcemanager.c",429,
> 2016-06-20 17:56:03.884424 
> CST,,,p526094,th5032941760,,,seg-1,"LOG","0","PostgreSQL 
> 8.2.15 (Greenplum Database 4.2.0 build 1) (HAWQ 2.0.0.0 build dev) on 
> x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.8.0 compiled on Jun 19 
> 2016 03:02:03",,,0,,"postmaster.c",3694,
> 2016-06-20 17:56:03.884441 
> CST,,,p526094,th5032941760,,,seg-1,"LOG","0","database system 
> is ready to accept connections","PostgreSQL 8.2.15 (Greenplum Database 4.2.0 
> build 1) (HAWQ 2.0.0.0 build dev) on 

[jira] [Commented] (HAWQ-837) Add python modules into HAWQ code except paramiko

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-837:
-

GitHub user radarwave opened a pull request:

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

HAWQ-837. Add python modules into HAWQ code

Added figleaf, pg8000, simplejson, pyyaml, lockfile, psi, pychecker, 
unittest2
Paramiko is not included because of License concern.
Pycrypto is not included because not in use anymore.

This will save user's time to install python modules by themselves.

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

$ git pull https://github.com/radarwave/incubator-hawq python3

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

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


commit 80e25b468cecb12fd58d28b5c08494ead7dbba81
Author: rlei 
Date:   2016-06-20T08:49:13Z

HAWQ-837. Add python modules into HAWQ code

Added figleaf, pg8000, simplejson, pyyaml, lockfile, psi, pychecker, 
unittest2
Paramiko is not included because of License concern.
Pycrypto is not included because not in use anymore.




> Add python modules into HAWQ code except paramiko
> -
>
> Key: HAWQ-837
> URL: https://issues.apache.org/jira/browse/HAWQ-837
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Build
>Reporter: Radar Lei
>Assignee: Lei Chang
>
> Add below python modules which compatible with Apache HAWQ license. Paramiko 
> won't be added.
> figleaf   BSD
> pg8000BSD
> pygresql  Python
> simplejsonMIT
> pyyamlMIT
> lockfile  OSI Approved :: MIT License
> psi   MIT
> pychecker BSD-like
> unittest2 OSI Approved :: BSD License
> pycrypto  Public domain



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

[GitHub] incubator-hawq pull request #735: HAWQ-837. Add python modules into HAWQ cod...

[radarwave]

GitHub user radarwave opened a pull request:

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

HAWQ-837. Add python modules into HAWQ code

Added figleaf, pg8000, simplejson, pyyaml, lockfile, psi, pychecker, 
unittest2
Paramiko is not included because of License concern.
Pycrypto is not included because not in use anymore.

This will save user's time to install python modules by themselves.

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

$ git pull https://github.com/radarwave/incubator-hawq python3

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

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


commit 80e25b468cecb12fd58d28b5c08494ead7dbba81
Author: rlei 
Date:   2016-06-20T08:49:13Z

HAWQ-837. Add python modules into HAWQ code

Added figleaf, pg8000, simplejson, pyyaml, lockfile, psi, pychecker, 
unittest2
Paramiko is not included because of License concern.
Pycrypto is not included because not in use anymore.




---
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-841) Running "make -j8 unittest-check" under src/backend will throw "File exists" error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-841:
-

Github user xunzhang commented on the issue:

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


> Running "make -j8 unittest-check" under src/backend will throw "File exists" 
> error
> --
>
> Key: HAWQ-841
> URL: https://issues.apache.org/jira/browse/HAWQ-841
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Tests
>Reporter: Paul Guo
>Assignee: Jiali Yao
>
> ERROR:root:Error has occurred during parsing 
> /home/build/incubator-hawq/src/backend/executor/execAmi.c: [Errno 17] File 
> exists: '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> Traceback (most recent call last):
>   File "mocker.py", line 307, in 
> main()
>   File "mocker.py", line 300, in main
> mock = MockFile(cfile, options)
>   File "mocker.py", line 121, in __init__
> self.outname = self.output_filename()
>   File "mocker.py", line 132, in output_filename
> os.makedirs(out_dir)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 17] File exists: 
> '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> mocking /home/build/incubator-hawq/src/backend/executor/execQual.c
> make[4]: *** 
> [../../../../../src/test/unit/mock/backend/executor/execAmi_mock.c] Error 1
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[3]: *** [mockup-phony] Error 2
> make[3]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[2]: *** [unittest-check] Error 2
> make[2]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common'
> make[1]: *** [unittest-check] Error 2
> make[1]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access'
> make: *** [unittest-check] Error 2



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

[GitHub] incubator-hawq issue #734: HAWQ-841. Running "make -j8 unittest-check" under...

[xunzhang]

Github user xunzhang commented on the issue:

https://github.com/apache/incubator-hawq/pull/734
  
+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-830) Wrong result in CTE query due to CTE is treated as init plan by planner and evaluated multiple times

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-830:
-

Github user zhangh43 commented on the issue:

https://github.com/apache/incubator-hawq/pull/731
  
GUC gp_cte_sharing cannot be false, and should be removed.
Because it's not consistent with CTE semantic(CTE should not be init plan 
more than once).


> Wrong result in CTE query due to CTE is treated as init plan by planner and 
> evaluated multiple times
> 
>
> Key: HAWQ-830
> URL: https://issues.apache.org/jira/browse/HAWQ-830
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Optimizer
>Reporter: Ruilong Huo
>Assignee: Ruilong Huo
>
> In CTE query, if the CTE itself is referenced multiple times, it should be 
> evaluated only once and then be used multiple time. However, it is treated as 
> init plan and evaluated multiple times in hawq 1.x and 2.0. This has two 
> issues here:
> 1. If the query in CTE is "volatile" (i.e., select volatile function) or has 
> side effect (create/drop object in database), it may generate wrong result
> 2. The performance of the query is not so efficient since the query in CTE is 
> evaluated multiple times.
> Here is the steps to reproduce:
> 1) in hawq, CTE is treated as init plan and evaluated 2 times. Thus, the 
> result is incorrect
> {noformat}
> WITH r AS (SELECT random())
> SELECT r1.*, r2.*
> FROM r AS r1, r AS r2;
>   random   |  random
> ---+---
>  0.519145511090755 | 0.751198637764901
> (1 row)
> EXPLAIN
> WITH r AS (SELECT random())
> SELECT r1.*, r2.*
> FROM r AS r1, r AS r2;
>   QUERY PLAN
> --
>  Nested Loop  (cost=0.04..0.77 rows=20 width=16)
>->  Result  (cost=0.01..0.02 rows=1 width=0)
>  InitPlan
>->  Result  (cost=0.00..0.01 rows=1 width=0)
>->  Materialize  (cost=0.03..0.09 rows=6 width=8)
>  ->  Result  (cost=0.01..0.02 rows=1 width=0)
>InitPlan
>  ->  Result  (cost=0.00..0.01 rows=1 width=0)
>  Settings:  default_hash_table_bucket_number=6
>  Optimizer status: legacy query optimizer
> (10 rows)
> {noformat}
> 2) in postgres, CTE is treated as CTE scan and evaluated 1 time. Thus, the 
> result is i
> {noformat}
> WITH r AS (SELECT random())
> SELECT r1.*, r2.*
> FROM r AS r1, r AS r2;
>   random   |  random
> ---+---
>  0.989214501809329 | 0.989214501809329
> (1 row)
> EXPLAIN
> WITH r AS (SELECT random())
> SELECT r1.*, r2.*
> FROM r AS r1, r AS r2;
> QUERY PLAN
> --
>  Nested Loop  (cost=0.01..0.06 rows=1 width=16)
>CTE r
>  ->  Result  (cost=0.00..0.01 rows=1 width=0)
>->  CTE Scan on r r1  (cost=0.00..0.02 rows=1 width=8)
>->  CTE Scan on r r2  (cost=0.00..0.02 rows=1 width=8)
> (5 rows){noformat}



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

[GitHub] incubator-hawq issue #731: HAWQ-830. Fix wrong result in CTE query due to CT...

[zhangh43]

Github user zhangh43 commented on the issue:

https://github.com/apache/incubator-hawq/pull/731
  
GUC gp_cte_sharing cannot be false, and should be removed.
Because it's not consistent with CTE semantic(CTE should not be init plan 
more than once).


---
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-841) Running "make -j8 unittest-check" under src/backend will throw "File exists" error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-841:
-

Github user yaoj2 commented on the issue:

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


> Running "make -j8 unittest-check" under src/backend will throw "File exists" 
> error
> --
>
> Key: HAWQ-841
> URL: https://issues.apache.org/jira/browse/HAWQ-841
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Tests
>Reporter: Paul Guo
>Assignee: Jiali Yao
>
> ERROR:root:Error has occurred during parsing 
> /home/build/incubator-hawq/src/backend/executor/execAmi.c: [Errno 17] File 
> exists: '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> Traceback (most recent call last):
>   File "mocker.py", line 307, in 
> main()
>   File "mocker.py", line 300, in main
> mock = MockFile(cfile, options)
>   File "mocker.py", line 121, in __init__
> self.outname = self.output_filename()
>   File "mocker.py", line 132, in output_filename
> os.makedirs(out_dir)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 17] File exists: 
> '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> mocking /home/build/incubator-hawq/src/backend/executor/execQual.c
> make[4]: *** 
> [../../../../../src/test/unit/mock/backend/executor/execAmi_mock.c] Error 1
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[3]: *** [mockup-phony] Error 2
> make[3]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[2]: *** [unittest-check] Error 2
> make[2]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common'
> make[1]: *** [unittest-check] Error 2
> make[1]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access'
> make: *** [unittest-check] Error 2



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

[GitHub] incubator-hawq issue #734: HAWQ-841. Running "make -j8 unittest-check" under...

[yaoj2]

Github user yaoj2 commented on the issue:

https://github.com/apache/incubator-hawq/pull/734
  
+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] [Resolved] (HAWQ-839) Libyarn coredump when failover to standby RM

[Lin Wen (JIRA)]

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

Lin Wen resolved HAWQ-839.
--
Resolution: Fixed

> Libyarn coredump when failover to standby RM
> 
>
> Key: HAWQ-839
> URL: https://issues.apache.org/jira/browse/HAWQ-839
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: libyarn
>Reporter: Lin Wen
>Assignee: Lin Wen
>
> Start hawq with yarn mode and kill Hadoop Yarn resource manager, coredump 
> happens, the stack is below: 
> #0  0x003e054325e5 in raise () from /lib64/libc.so.6
> #1  0x003e05433dc5 in abort () from /lib64/libc.so.6
> #2  0x7f04980b1109 in libyarn::HandleYarnFailoverException (e=...)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:170
> #3  0x7f04980b3211 in libyarn::ApplicationClient::getNewApplication 
> (this=0x1f17cd0)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:215
> #4  0x7f049809d639 in libyarn::LibYarnClient::createJob (this=0x1f1e500, 
> jobName="hawq", queue="default",
> jobId="")
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClient.cpp:163
> #5  0x7f04980987b8 in createJob (client=0x1f25950, jobName=Unhandled 
> dwarf expression opcode 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:61
> #6  createJob (client=0x1f25950, jobName=Unhandled dwarf expression opcode 
> 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:180
> #7  0x008e1117 in RB2YARN_registerYARNApplication ()
> #8  0x008e31ad in RB2YARN_initializeConnection ()
> #9  0x008e358b in ResBrokerMainInternal ()
> #10 0x008e38e8 in ResBrokerMain ()
> #11 0x008dfb66 in RB_LIBYARN_start ()
> #12 0x0090ae5e in MainHandlerLoop ()
> #13 0x0090b46a in ResManagerMainServer2ndPhase ()
> #14 0x0090ba14 in ResManagerMain ()
> #15 0x0090bd71 in ResManagerProcessStartup ()
> #16 0x00767f98 in CommenceNormalOperations ()
> #17 0x00768d44 in do_reaper ()
> #18 0x0076dbed in ServerLoop ()
> #19 0x0076f73e in PostmasterMain ()
> #20 0x006c828a in main ()



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

[jira] [Commented] (HAWQ-839) Libyarn coredump when failover to standby RM

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-839:
-

Github user linwen closed the pull request at:

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


> Libyarn coredump when failover to standby RM
> 
>
> Key: HAWQ-839
> URL: https://issues.apache.org/jira/browse/HAWQ-839
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: libyarn
>Reporter: Lin Wen
>Assignee: Lin Wen
>
> Start hawq with yarn mode and kill Hadoop Yarn resource manager, coredump 
> happens, the stack is below: 
> #0  0x003e054325e5 in raise () from /lib64/libc.so.6
> #1  0x003e05433dc5 in abort () from /lib64/libc.so.6
> #2  0x7f04980b1109 in libyarn::HandleYarnFailoverException (e=...)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:170
> #3  0x7f04980b3211 in libyarn::ApplicationClient::getNewApplication 
> (this=0x1f17cd0)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:215
> #4  0x7f049809d639 in libyarn::LibYarnClient::createJob (this=0x1f1e500, 
> jobName="hawq", queue="default",
> jobId="")
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClient.cpp:163
> #5  0x7f04980987b8 in createJob (client=0x1f25950, jobName=Unhandled 
> dwarf expression opcode 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:61
> #6  createJob (client=0x1f25950, jobName=Unhandled dwarf expression opcode 
> 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:180
> #7  0x008e1117 in RB2YARN_registerYARNApplication ()
> #8  0x008e31ad in RB2YARN_initializeConnection ()
> #9  0x008e358b in ResBrokerMainInternal ()
> #10 0x008e38e8 in ResBrokerMain ()
> #11 0x008dfb66 in RB_LIBYARN_start ()
> #12 0x0090ae5e in MainHandlerLoop ()
> #13 0x0090b46a in ResManagerMainServer2ndPhase ()
> #14 0x0090ba14 in ResManagerMain ()
> #15 0x0090bd71 in ResManagerProcessStartup ()
> #16 0x00767f98 in CommenceNormalOperations ()
> #17 0x00768d44 in do_reaper ()
> #18 0x0076dbed in ServerLoop ()
> #19 0x0076f73e in PostmasterMain ()
> #20 0x006c828a in main ()



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

[GitHub] incubator-hawq pull request #733: HAWQ-839. Fix libyarn coredump when failov...

[linwen]

Github user linwen closed the pull request at:

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


---
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-842) Failed to acquire resource from resource manager

[Lei Chang (JIRA)]

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

Lei Chang commented on HAWQ-842:


can you give more information on the version you used, and is there a core dump 
generated, and what is the scenario when this issue happens?

> Failed to acquire resource from resource manager
> 
>
> Key: HAWQ-842
> URL: https://issues.apache.org/jira/browse/HAWQ-842
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Bill Wailliam
>Assignee: Lei Chang
>
> This is the pg_log:
> 2016-06-20 17:56:03.864644 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","database system 
> was shut down at 2016-06-20 17:54:32 CST",,,0,,"xlog.c",6205,
> 2016-06-20 17:56:03.864908 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","checkpoint 
> record is at 0/2672EF8",,,0,,"xlog.c",6304,
> 2016-06-20 17:56:03.864923 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","redo record is 
> at 0/2672EF8; undo record is at 0/0; shutdown TRUE",,,0,,"xlog.c",6338,
> 2016-06-20 17:56:03.864933 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","next 
> transaction ID: 0/1284; next OID: 16514",,,0,,"xlog.c",6342,
> 2016-06-20 17:56:03.864942 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","next 
> MultiXactId: 1; next MultiXactOffset: 0",,,0,,"xlog.c",6345,
> 2016-06-20 17:56:03.864951 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","end of 
> transaction log location is 0/2672F48",,,0,,"xlog.c",6582,
> 2016-06-20 17:56:03.865750 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","Oldest active 
> transaction from prepared transactions 1284",,,0,,"xlog.c",5996,
> 2016-06-20 17:56:03.867372 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","database system 
> is ready",,,0,,"xlog.c",6022,
> 2016-06-20 17:56:03.867394 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","PostgreSQL 
> 8.2.15 (Greenplum Database 4.2.0 build 1) (HAWQ 2.0.0.0 build dev) on 
> x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.8.0 compiled on Jun 19 
> 2016 03:02:01",,,0,,"xlog.c",6032,
> 2016-06-20 17:56:03.868503 
> CST,,,p526096,th5032941760,,,seg-1,"LOG","0","Finished normal 
> startup for clean shutdown case",,,0,,"xlog.c",6810,
> 2016-06-20 17:56:03.876213 
> CST,,,p526097,th5032941760,,,seg-1,"LOG","0","Finished 
> startup integrity checking",,,0,,"xlog.c",7159,
> 2016-06-20 17:56:03.879998 
> CST,,,p526104,th5032941760,,,seg-1,"LOG","0","HAWQ Segment RM 
> :: Temporary directory /data1/hawq/tmp",,,0,,"resourcemanager.c",1055,
> 2016-06-20 17:56:03.880039 
> CST,,,p526104,th5032941760,,,seg-1,"LOG","0","checkAndBuildFailedTmpDirList
>  finished checking temporary directory, which costs 41 
> us",,,0,,"resourcemanager_RMSEG.c",274,
> 2016-06-20 17:56:03.883958 
> CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","YARN mode 
> resource broker created resource broker process 
> PID=526105.",,,0,,"resourcebroker_LIBYARN.c",158,
> 2016-06-20 17:56:03.884155 
> CST,,,p526105,th5032941760,con4,,seg-1,"LOG","0","YARN mode 
> resource broker accepted YARN connection arguments : YARN Server 
> RM_IP_XX:8032 Scheduler server RM_IP_XX:8030 Queue hawq Application 
> name hawq, by user:postgres",,,0,,"resourcebroker_LIBYARN_proc.c",501,
> 2016-06-20 17:56:03.884283 
> CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","Resource 
> manager starts accepting resource request. Listening normal socket port 5437. 
> Total listened 1 FDs.",,,0,,"resourcemanager.c",2492,
> 2016-06-20 17:56:03.884378 
> CST,,,p526094,th5032941760,,,seg-1,"LOG","0","Wait for HAWQ 
> RM -1",,,0,,"resourcemanager.c",421,
> 2016-06-20 17:56:03.884409 
> CST,,,p526094,th5032941760,,,seg-1,"LOG","0","HAWQ :: 
> Received signal notification that HAWQ RM works 
> now.",,,0,,"resourcemanager.c",429,
> 2016-06-20 17:56:03.884424 
> CST,,,p526094,th5032941760,,,seg-1,"LOG","0","PostgreSQL 
> 8.2.15 (Greenplum Database 4.2.0 build 1) (HAWQ 2.0.0.0 build dev) on 
> x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.8.0 compiled on Jun 19 
> 2016 03:02:03",,,0,,"postmaster.c",3694,
> 2016-06-20 17:56:03.884441 
> CST,,,p526094,th5032941760,,,seg-1,"LOG","0","database system 
> is ready to accept connections","PostgreSQL 8.2.15 (Greenplum Database 4.2.0 
> build 1) (HAWQ 2.0.0.0 build dev) on x86_64-unknown-linux-gnu, compiled by 
> GCC gcc (GCC) 4.8.0 compiled on Jun 19 2016 
> 03:02:03",,0,,"postmaster.c",3701,
> 2016-06-20 

[jira] [Commented] (HAWQ-833) Lack of pgcrypto.sql for the pgcrypto support

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-833:
-

Github user zhangh43 commented on the issue:

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


> Lack of pgcrypto.sql for the pgcrypto support
> -
>
> Key: HAWQ-833
> URL: https://issues.apache.org/jira/browse/HAWQ-833
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Paul Guo
>Assignee: Lei Chang
>
> Currently we use upstream postgres/pgcrypto for the pgcrypto support. The 
> version we are using just provides the sql file for the "create extension" 
> command which has not been supported on our code. We need to provide a 
> separate  pgcrypto.sql (and its corresponding uninstall sql file), just like 
> what pl/plr code does, then users could use the pgcrypto functionality as 
> before.



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

[GitHub] incubator-hawq issue #732: HAWQ-833. Lack of pgcrypto.sql for the pgcrypto s...

[zhangh43]

Github user zhangh43 commented on the issue:

https://github.com/apache/incubator-hawq/pull/732
  
+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-842) Failed to acquire resource from resource manager

[Bill Wailliam (JIRA)]

Bill Wailliam created HAWQ-842:
--

 Summary: Failed to acquire resource from resource manager
 Key: HAWQ-842
 URL: https://issues.apache.org/jira/browse/HAWQ-842
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Resource Manager
Reporter: Bill Wailliam
Assignee: Lei Chang


This is the pg_log:
2016-06-20 17:56:03.864644 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","database system 
was shut down at 2016-06-20 17:54:32 CST",,,0,,"xlog.c",6205,
2016-06-20 17:56:03.864908 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","checkpoint record 
is at 0/2672EF8",,,0,,"xlog.c",6304,
2016-06-20 17:56:03.864923 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","redo record is at 
0/2672EF8; undo record is at 0/0; shutdown TRUE",,,0,,"xlog.c",6338,
2016-06-20 17:56:03.864933 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","next transaction 
ID: 0/1284; next OID: 16514",,,0,,"xlog.c",6342,
2016-06-20 17:56:03.864942 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","next MultiXactId: 
1; next MultiXactOffset: 0",,,0,,"xlog.c",6345,
2016-06-20 17:56:03.864951 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","end of 
transaction log location is 0/2672F48",,,0,,"xlog.c",6582,
2016-06-20 17:56:03.865750 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","Oldest active 
transaction from prepared transactions 1284",,,0,,"xlog.c",5996,
2016-06-20 17:56:03.867372 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","database system 
is ready",,,0,,"xlog.c",6022,
2016-06-20 17:56:03.867394 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","PostgreSQL 8.2.15 
(Greenplum Database 4.2.0 build 1) (HAWQ 2.0.0.0 build dev) on 
x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.8.0 compiled on Jun 19 
2016 03:02:01",,,0,,"xlog.c",6032,
2016-06-20 17:56:03.868503 
CST,,,p526096,th5032941760,,,seg-1,"LOG","0","Finished normal 
startup for clean shutdown case",,,0,,"xlog.c",6810,
2016-06-20 17:56:03.876213 
CST,,,p526097,th5032941760,,,seg-1,"LOG","0","Finished startup 
integrity checking",,,0,,"xlog.c",7159,
2016-06-20 17:56:03.879998 
CST,,,p526104,th5032941760,,,seg-1,"LOG","0","HAWQ Segment RM 
:: Temporary directory /data1/hawq/tmp",,,0,,"resourcemanager.c",1055,
2016-06-20 17:56:03.880039 
CST,,,p526104,th5032941760,,,seg-1,"LOG","0","checkAndBuildFailedTmpDirList
 finished checking temporary directory, which costs 41 
us",,,0,,"resourcemanager_RMSEG.c",274,
2016-06-20 17:56:03.883958 
CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","YARN mode 
resource broker created resource broker process 
PID=526105.",,,0,,"resourcebroker_LIBYARN.c",158,
2016-06-20 17:56:03.884155 
CST,,,p526105,th5032941760,con4,,seg-1,"LOG","0","YARN mode 
resource broker accepted YARN connection arguments : YARN Server 
RM_IP_XX:8032 Scheduler server RM_IP_XX:8030 Queue hawq Application 
name hawq, by user:postgres",,,0,,"resourcebroker_LIBYARN_proc.c",501,
2016-06-20 17:56:03.884283 
CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","Resource 
manager starts accepting resource request. Listening normal socket port 5437. 
Total listened 1 FDs.",,,0,,"resourcemanager.c",2492,
2016-06-20 17:56:03.884378 
CST,,,p526094,th5032941760,,,seg-1,"LOG","0","Wait for HAWQ RM 
-1",,,0,,"resourcemanager.c",421,
2016-06-20 17:56:03.884409 
CST,,,p526094,th5032941760,,,seg-1,"LOG","0","HAWQ :: Received 
signal notification that HAWQ RM works now.",,,0,,"resourcemanager.c",429,
2016-06-20 17:56:03.884424 
CST,,,p526094,th5032941760,,,seg-1,"LOG","0","PostgreSQL 8.2.15 
(Greenplum Database 4.2.0 build 1) (HAWQ 2.0.0.0 build dev) on 
x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.8.0 compiled on Jun 19 
2016 03:02:03",,,0,,"postmaster.c",3694,
2016-06-20 17:56:03.884441 
CST,,,p526094,th5032941760,,,seg-1,"LOG","0","database system 
is ready to accept connections","PostgreSQL 8.2.15 (Greenplum Database 4.2.0 
build 1) (HAWQ 2.0.0.0 build dev) on x86_64-unknown-linux-gnu, compiled by GCC 
gcc (GCC) 4.8.0 compiled on Jun 19 2016 03:02:03",,0,,"postmaster.c",3701,
2016-06-20 17:56:03.885673 
CST,,,p526095,th5032941760,,,seg-1,"LOG","0","3rd party error 
log:
2016-06-20 17:56:03.885486, p526105, th140510358382816, INFO ApplicationClient 
session auth method : simple""SysLoggerMain","syslogger.c",518,
2016-06-20 17:56:03.892215 
CST,,,p526104,th5032941760,con4,,seg-1,"LOG","0","Cleanup 
segment configuration catalog table 
successfully!",,,0,,"resourcepool.c",460,
2016-06-20 17:56:03.892604 

[jira] [Commented] (HAWQ-839) Libyarn coredump when failover to standby RM

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-839:
-

Github user huor commented on the issue:

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


> Libyarn coredump when failover to standby RM
> 
>
> Key: HAWQ-839
> URL: https://issues.apache.org/jira/browse/HAWQ-839
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: libyarn
>Reporter: Lin Wen
>Assignee: Lin Wen
>
> Start hawq with yarn mode and kill Hadoop Yarn resource manager, coredump 
> happens, the stack is below: 
> #0  0x003e054325e5 in raise () from /lib64/libc.so.6
> #1  0x003e05433dc5 in abort () from /lib64/libc.so.6
> #2  0x7f04980b1109 in libyarn::HandleYarnFailoverException (e=...)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:170
> #3  0x7f04980b3211 in libyarn::ApplicationClient::getNewApplication 
> (this=0x1f17cd0)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:215
> #4  0x7f049809d639 in libyarn::LibYarnClient::createJob (this=0x1f1e500, 
> jobName="hawq", queue="default",
> jobId="")
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClient.cpp:163
> #5  0x7f04980987b8 in createJob (client=0x1f25950, jobName=Unhandled 
> dwarf expression opcode 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:61
> #6  createJob (client=0x1f25950, jobName=Unhandled dwarf expression opcode 
> 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:180
> #7  0x008e1117 in RB2YARN_registerYARNApplication ()
> #8  0x008e31ad in RB2YARN_initializeConnection ()
> #9  0x008e358b in ResBrokerMainInternal ()
> #10 0x008e38e8 in ResBrokerMain ()
> #11 0x008dfb66 in RB_LIBYARN_start ()
> #12 0x0090ae5e in MainHandlerLoop ()
> #13 0x0090b46a in ResManagerMainServer2ndPhase ()
> #14 0x0090ba14 in ResManagerMain ()
> #15 0x0090bd71 in ResManagerProcessStartup ()
> #16 0x00767f98 in CommenceNormalOperations ()
> #17 0x00768d44 in do_reaper ()
> #18 0x0076dbed in ServerLoop ()
> #19 0x0076f73e in PostmasterMain ()
> #20 0x006c828a in main ()



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

[GitHub] incubator-hawq issue #644: Remove traceflag that allows ORCA to run in multi...

[vraghavan78]

Github user vraghavan78 commented on the issue:

https://github.com/apache/incubator-hawq/pull/644
  
@liming01 @changleicn please answer @ictmalili question


---
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-841) Running "make -j8 unittest-check" under src/backend will throw "File exists" error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-841:
-

GitHub user paul-guo- opened a pull request:

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

HAWQ-841. Running "make -j8 unittest-check" under src/backend will throw 
"File exists" error

Typical race condition issue.

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

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

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

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


commit 2d69976929bd63d11ddc90c3766206f3b09ef2a2
Author: Paul Guo 
Date:   2016-06-20T10:00:08Z

HAWQ-841. Running "make -j8 unittest-check" under src/backend will throw 
"File exists" error




> Running "make -j8 unittest-check" under src/backend will throw "File exists" 
> error
> --
>
> Key: HAWQ-841
> URL: https://issues.apache.org/jira/browse/HAWQ-841
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Tests
>Reporter: Paul Guo
>Assignee: Jiali Yao
>
> ERROR:root:Error has occurred during parsing 
> /home/build/incubator-hawq/src/backend/executor/execAmi.c: [Errno 17] File 
> exists: '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> Traceback (most recent call last):
>   File "mocker.py", line 307, in 
> main()
>   File "mocker.py", line 300, in main
> mock = MockFile(cfile, options)
>   File "mocker.py", line 121, in __init__
> self.outname = self.output_filename()
>   File "mocker.py", line 132, in output_filename
> os.makedirs(out_dir)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 17] File exists: 
> '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> mocking /home/build/incubator-hawq/src/backend/executor/execQual.c
> make[4]: *** 
> [../../../../../src/test/unit/mock/backend/executor/execAmi_mock.c] Error 1
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[3]: *** [mockup-phony] Error 2
> make[3]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[2]: *** [unittest-check] Error 2
> make[2]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common'
> make[1]: *** [unittest-check] Error 2
> make[1]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access'
> make: *** [unittest-check] Error 2



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

[GitHub] incubator-hawq pull request #734: HAWQ-841. Running "make -j8 unittest-check...

[paul-guo-]

GitHub user paul-guo- opened a pull request:

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

HAWQ-841. Running "make -j8 unittest-check" under src/backend will throw 
"File exists" error

Typical race condition issue.

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

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

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

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


commit 2d69976929bd63d11ddc90c3766206f3b09ef2a2
Author: Paul Guo 
Date:   2016-06-20T10:00:08Z

HAWQ-841. Running "make -j8 unittest-check" under src/backend will throw 
"File exists" error




---
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-841) Running "make -j8 unittest-check" under src/backend will throw "File exists" error

[Paul Guo (JIRA)]

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

Paul Guo updated HAWQ-841:
--
Summary: Running "make -j8 unittest-check" under src/backend will throw 
"File exists" error  (was: Running "make -j8 unittest-check" under src/backedn 
will throw "File exists error")

> Running "make -j8 unittest-check" under src/backend will throw "File exists" 
> error
> --
>
> Key: HAWQ-841
> URL: https://issues.apache.org/jira/browse/HAWQ-841
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Tests
>Reporter: Paul Guo
>Assignee: Jiali Yao
>
> ERROR:root:Error has occurred during parsing 
> /home/build/incubator-hawq/src/backend/executor/execAmi.c: [Errno 17] File 
> exists: '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> Traceback (most recent call last):
>   File "mocker.py", line 307, in 
> main()
>   File "mocker.py", line 300, in main
> mock = MockFile(cfile, options)
>   File "mocker.py", line 121, in __init__
> self.outname = self.output_filename()
>   File "mocker.py", line 132, in output_filename
> os.makedirs(out_dir)
>   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 17] File exists: 
> '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
> mocking /home/build/incubator-hawq/src/backend/executor/execQual.c
> make[4]: *** 
> [../../../../../src/test/unit/mock/backend/executor/execAmi_mock.c] Error 1
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[3]: *** [mockup-phony] Error 2
> make[3]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
> make[2]: *** [unittest-check] Error 2
> make[2]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access/common'
> make[1]: *** [unittest-check] Error 2
> make[1]: Leaving directory 
> `/tmp/build/78017950/incubator-hawq/src/backend/access'
> make: *** [unittest-check] Error 2



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

[jira] [Created] (HAWQ-841) Running "make -j8 unittest-check" under src/backedn will throw "File exists error"

[Paul Guo (JIRA)]

Paul Guo created HAWQ-841:
-

 Summary: Running "make -j8 unittest-check" under src/backedn will 
throw "File exists error"
 Key: HAWQ-841
 URL: https://issues.apache.org/jira/browse/HAWQ-841
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Tests
Reporter: Paul Guo
Assignee: Jiali Yao


ERROR:root:Error has occurred during parsing 
/home/build/incubator-hawq/src/backend/executor/execAmi.c: [Errno 17] File 
exists: '/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
Traceback (most recent call last):
  File "mocker.py", line 307, in 
main()
  File "mocker.py", line 300, in main
mock = MockFile(cfile, options)
  File "mocker.py", line 121, in __init__
self.outname = self.output_filename()
  File "mocker.py", line 132, in output_filename
os.makedirs(out_dir)
  File "/usr/lib64/python2.6/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: 
'/home/build/incubator-hawq/src/test/unit/mock/backend/executor'
mocking /home/build/incubator-hawq/src/backend/executor/execQual.c
make[4]: *** 
[../../../../../src/test/unit/mock/backend/executor/execAmi_mock.c] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory 
`/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
make[3]: *** [mockup-phony] Error 2
make[3]: Leaving directory 
`/tmp/build/78017950/incubator-hawq/src/backend/access/common/test'
make[2]: *** [unittest-check] Error 2
make[2]: Leaving directory 
`/tmp/build/78017950/incubator-hawq/src/backend/access/common'
make[1]: *** [unittest-check] Error 2
make[1]: Leaving directory 
`/tmp/build/78017950/incubator-hawq/src/backend/access'
make: *** [unittest-check] Error 2





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

[jira] [Created] (HAWQ-840) Partition Sort Support

[Lei Chang (JIRA)]

Lei Chang created HAWQ-840:
--

 Summary: Partition Sort Support
 Key: HAWQ-840
 URL: https://issues.apache.org/jira/browse/HAWQ-840
 Project: Apache HAWQ
  Issue Type: Wish
Reporter: Lei Chang
Assignee: Lei Chang


Support the partition sort as a new method for sorting.



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

[jira] [Updated] (HAWQ-101) Remove postgres version number from HAWQ

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-101:
---
Issue Type: Wish  (was: Task)

> Remove postgres version number from HAWQ 
> -
>
> Key: HAWQ-101
> URL: https://issues.apache.org/jira/browse/HAWQ-101
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: Command Line Tools
>Reporter: Goden Yao
>Assignee: Lei Chang
>Priority: Minor
>  Labels: OSS
> Fix For: backlog
>
>
> Some version numbers showing in command line is due to historical reason that 
> HAWQ is derived from Greenplum and postgres.
> It doesn't make sense to have these version numbers which would confuse users 
> after open source.
> {code:actionscript}
> gpadmin@rhel65-1 ~]$ psql --version
> psql (PostgreSQL) 8.2.15
> contains support for command-line editing
> {code}
> {code:actionscript}
> [gpadmin@rhel65-1 ~]$ postgres --version
> postgres (HAWQ) 8.2.15
> {code}
> {code:actionscript}
> [gpadmin@rhel65-1 ~]$ postgres --hawq-version
> postgres (HAWQ) 2.0.0.0 build dev
> {code}
> {code:actionscript}
> [gpadmin@rhel65-1 ~]$ postgres --gp-version
> postgres (HAWQ) 4.2.0 build 1
> {code}



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

[jira] [Closed] (HAWQ-490) Add version and compatibility detection for HAWQ + GPORCA

[Lei Chang (JIRA)]

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

Lei Chang closed HAWQ-490.
--
Resolution: Won't Fix

> Add version and compatibility detection for HAWQ + GPORCA
> -
>
> Key: HAWQ-490
> URL: https://issues.apache.org/jira/browse/HAWQ-490
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build
>Reporter: Jacob Max Frank
>Assignee: Lei Chang
>Priority: Minor
>
> Autoconf should be able to detect GPORCA version information and check for 
> compatibility with the version of HAWQ being built.  Additionally, running 
> {{select gp_opt_version();}} on HAWQ compiled with GPORCA should output 
> correct version information for its components (GPOPT, GPOS, and GPXerces).
> [~rvs] suggested using {{pkgutil}}.  Alternate potential strategies include 
> using a {{git submodule}} or pulling values from a {{version.h}} file.



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

[jira] [Updated] (HAWQ-98) Moving HAWQ docker file into code base

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-98:
--
Issue Type: Wish  (was: Task)

> Moving HAWQ docker file into code base
> --
>
> Key: HAWQ-98
> URL: https://issues.apache.org/jira/browse/HAWQ-98
> Project: Apache HAWQ
>  Issue Type: Wish
>Reporter: Goden Yao
>Assignee: Roman Shaposhnik
> Fix For: 2.1.0
>
>
> We have a pre-built docker image (check [HAWQ build & 
> install|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61320026]
>  sitting outside the codebase.
> It should be incorporated in the Apache git and maintained by the community.
> Proposed location is to create a  folder under root



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

[jira] [Updated] (HAWQ-99) OpenSSL 0.9.x to 1.x upgrade

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-99:
--
Issue Type: New Feature  (was: Wish)

> OpenSSL 0.9.x to 1.x upgrade
> 
>
> Key: HAWQ-99
> URL: https://issues.apache.org/jira/browse/HAWQ-99
> Project: Apache HAWQ
>  Issue Type: New Feature
>Reporter: Goden Yao
>Assignee: Lei Chang
> Fix For: backlog
>
>
> 0.9.x product line will be deprecated by end of 2015.
> We need to move to the new 1.x product line.



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

[jira] [Updated] (HAWQ-99) OpenSSL 0.9.x to 1.x upgrade

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-99:
--
Issue Type: Wish  (was: Improvement)

> OpenSSL 0.9.x to 1.x upgrade
> 
>
> Key: HAWQ-99
> URL: https://issues.apache.org/jira/browse/HAWQ-99
> Project: Apache HAWQ
>  Issue Type: Wish
>Reporter: Goden Yao
>Assignee: Lei Chang
> Fix For: backlog
>
>
> 0.9.x product line will be deprecated by end of 2015.
> We need to move to the new 1.x product line.



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

[jira] [Updated] (HAWQ-122) FILESPACE URL in pg_filespace_entry is confusing

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-122:
---
Issue Type: Wish  (was: Improvement)

> FILESPACE URL in pg_filespace_entry is confusing
> 
>
> Key: HAWQ-122
> URL: https://issues.apache.org/jira/browse/HAWQ-122
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: Storage
>Reporter: Lirong Jian
>Assignee: Lirong Jian
> Fix For: backlog
>
>
> postgres=# SELECT * FROM pg_filespace_entry;
>  fsefsoid | fsedbid | fselocation  
> --+-+--
> 16384 |   0 | hdfs://Lirong-MBP:9000/gpsql
> (1 row)
> postgres=# CREATE FILESPACE fs_1 ON HDFS (
> postgres(# 'Lirong-MBP:9000/hawq/fs_1');
> CREATE FILESPACE
> postgres=# CREATE FILESPACE fs_2 ON HDFS (
>   
>
> 'Lirong-MBP:9000/hawq/fs_2') WITH (NUMREPLICA=2);
> CREATE FILESPACE
> postgres=# CREATE FILESPACE fs_3 ON HDFS (
>   
>
> 'Lirong-MBP:9000/hawq/fs_3') WITH (NUMREPLICA=3);
> CREATE FILESPACE
> postgres=# SELECT * FROM pg_filespace_entry;
>  fsefsoid | fsedbid | fselocation 
> --+-+-
> 16384 |   0 | hdfs://Lirong-MBP:9000/gpsql
> 16532 |   0 | hdfs://Lirong-MBP:9000/hawq/fs_1
> 16533 |   0 | hdfs://{replica=2}Lirong-MBP:9000/hawq/fs_2
> 16534 |   0 | hdfs://{replica=3}Lirong-MBP:9000/hawq/fs_3
> (4 rows)
> The {replica=3} option is very confusing. It is not a valid HDSF url, which 
> means we can only access that URL through external tools such as hdfs, 
> although it is valid inside HAWQ (we exclude that part when we are really 
> going to access that path).



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

[jira] [Closed] (HAWQ-144) Build HAWQ on MacOS

[Lei Chang (JIRA)]

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

Lei Chang closed HAWQ-144.
--
   Resolution: Fixed
Fix Version/s: (was: 2.1.0)
   2.0.0

> Build HAWQ on MacOS
> ---
>
> Key: HAWQ-144
> URL: https://issues.apache.org/jira/browse/HAWQ-144
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Build
>Reporter: Lei Chang
>Assignee: Lei Chang
> Fix For: 2.0.0
>
>
> Currently, the only tested build platform for HAWQ is redhat 6.x. It will be 
> very nice if it can work on Mac with clang. This will make new contributions 
> much easier.
> Instructions on building HAWQ on linux is at: 
> https://github.com/apache/incubator-hawq/blob/master/BUILD_INSTRUCTIONS.md



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

[jira] [Updated] (HAWQ-124) Create Project Maturity Model summary file

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-124:
---
Issue Type: Improvement  (was: Task)

> Create Project Maturity Model summary file
> --
>
> Key: HAWQ-124
> URL: https://issues.apache.org/jira/browse/HAWQ-124
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Core
>Reporter: Caleb Welton
>Assignee: Lei Chang
> Fix For: 2.1.0
>
>
> Graduating from an Apache Incubator project requires showing the Apache 
> Incubator IPMC that we have reached a level of maturity as an incubator 
> project.  One tool that can be used to assess our maturity is the [Apache 
> Project Maturity Model 
> Document|https://community.apache.org/apache-way/apache-project-maturity-model.html].
>   
> I propose we do something similar to what Groovy did and include a Project 
> Maturity Self assessment in our source code and evaluate ourselves with 
> respect to project maturity with each of our reports.  
> To do:
> 1. Create a MATURITY.adoc file in our root project directory containing our 
> self assessment.
> See 
> https://github.com/apache/groovy/blob/67b87a3592f13a6281f5b20081c37a66c80079b9/MATURITY.adoc
>  as an example document in the Groovy project.



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

[jira] [Updated] (HAWQ-150) External tables can be designated for both READ and WRITE

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-150:
---
Issue Type: Wish  (was: New Feature)

> External tables can be designated for both READ and WRITE
> -
>
> Key: HAWQ-150
> URL: https://issues.apache.org/jira/browse/HAWQ-150
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: External Tables
>Reporter: C.J. Jameson
>Assignee: Lei Chang
> Fix For: 3.0.0
>
>
> Currently, external tables are either read-only or write-only when they are 
> created. We could support an external table with the capability for both 
> reads and writes.
> As pointed out by hawqst...@163.com



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

[jira] [Updated] (HAWQ-231) Alter table by drop all columns of it, then it has some interesting problems

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-231:
---
Issue Type: Bug  (was: Improvement)

> Alter table by drop all columns of it, then it has some interesting problems
> 
>
> Key: HAWQ-231
> URL: https://issues.apache.org/jira/browse/HAWQ-231
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Storage
>Reporter: Dong Li
>Assignee: Lei Chang
> Fix For: backlog
>
>
> It is a design behavior problem. 
> When we drop all the columns, should it truncate the table?
> Otherwise if the count of invisible rows has meaning.
> You can not see anything, but it shows that there are 1000 rows here.
> I know that in storage view and design view it is ok.
> But in  user view, it may be puzzled.
> {code}
> intern=# create table alterall (i int, j int);
> CREATE TABLE
> intern=# insert into alterall VALUES 
> (generate_series(1,1000),generate_series(1,2));
> INSERT 0 1000
> intern=# alter table alterall drop COLUMN i;
> ALTER TABLE
> intern=# alter TABLE alterall drop COLUMN j;
> ALTER TABLE
> intern=# select * from alterall ;
> --
> (1000 rows)
> intern=# alter TABLE alterall add column k int default 3;
> ALTER TABLE
> intern=# select * from alterall;
>  k
> ---
>  3
>  3
>  3
>  3
>  3
>  3
>  3
> ...
> (1000 rows)
> {code}



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

[jira] [Updated] (HAWQ-304) Support update and delete on non-heap tables

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-304:
---
Issue Type: Wish  (was: New Feature)

> Support update and delete on non-heap tables
> 
>
> Key: HAWQ-304
> URL: https://issues.apache.org/jira/browse/HAWQ-304
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: Storage
>Reporter: Lei Chang
> Fix For: 3.0.0
>
> Attachments: mutable_table.sql
>
>




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

[jira] [Resolved] (HAWQ-305) Support PostGIS

[Lei Chang (JIRA)]

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

Lei Chang resolved HAWQ-305.

   Resolution: Duplicate
Fix Version/s: (was: 2.1.0)

> Support PostGIS
> ---
>
> Key: HAWQ-305
> URL: https://issues.apache.org/jira/browse/HAWQ-305
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Unknown
>Reporter: Lei Chang
>




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

[jira] [Closed] (HAWQ-306) Direct hdfs data file drop & load to native HAWQ tables

[Lei Chang (JIRA)]

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

Lei Chang closed HAWQ-306.
--

> Direct hdfs data file drop & load to native HAWQ tables
> ---
>
> Key: HAWQ-306
> URL: https://issues.apache.org/jira/browse/HAWQ-306
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Storage
>Reporter: Lei Chang
> Fix For: 2.0.0
>
>
> Sometimes, users want to add existing hdfs files to native HAWQ tables. 
> Current method is to load data into the native tables. A lightweight method 
> is to directly move the files to the table directory. 
> With HAWQ 2.0 per table directory feature, this becomes less difficult.



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

[jira] [Closed] (HAWQ-307) Ubuntu Support

[Lei Chang (JIRA)]

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

Lei Chang closed HAWQ-307.
--

> Ubuntu Support
> --
>
> Key: HAWQ-307
> URL: https://issues.apache.org/jira/browse/HAWQ-307
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Build
>Reporter: Lei Chang
>Assignee: Clay B.
> Fix For: 2.0.0
>
>
> To support HAWQ running on Ubuntu OS 14.04.3



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

[jira] [Resolved] (HAWQ-308) S3 Integration

[Lei Chang (JIRA)]

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

Lei Chang resolved HAWQ-308.

Resolution: Duplicate

> S3 Integration
> --
>
> Key: HAWQ-308
> URL: https://issues.apache.org/jira/browse/HAWQ-308
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Storage
>Reporter: Lei Chang
> Fix For: 2.1.0
>
>
> There are two methods to support S3.
> 1. Support S3 as a native file system, so storing data on S3 is just like 
> storing data on HDFS.
> 2. Support S3 as an external storage. 



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

[jira] [Reopened] (HAWQ-308) S3 Integration

[Lei Chang (JIRA)]

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

Lei Chang reopened HAWQ-308:


> S3 Integration
> --
>
> Key: HAWQ-308
> URL: https://issues.apache.org/jira/browse/HAWQ-308
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Storage
>Reporter: Lei Chang
> Fix For: 2.1.0
>
>
> There are two methods to support S3.
> 1. Support S3 as a native file system, so storing data on S3 is just like 
> storing data on HDFS.
> 2. Support S3 as an external storage. 



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

[jira] [Updated] (HAWQ-309) Support Centos/RHEL 7

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-309:
---
Issue Type: Wish  (was: New Feature)

> Support Centos/RHEL 7 
> --
>
> Key: HAWQ-309
> URL: https://issues.apache.org/jira/browse/HAWQ-309
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: Build
>Reporter: Lei Chang
> Fix For: 2.1.0
>
>




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

[jira] [Updated] (HAWQ-319) REST API for HAWQ

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-319:
---
Issue Type: Wish  (was: New Feature)

> REST API for HAWQ
> -
>
> Key: HAWQ-319
> URL: https://issues.apache.org/jira/browse/HAWQ-319
> Project: Apache HAWQ
>  Issue Type: Wish
>Reporter: Lei Chang
> Fix For: backlog
>
>




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

[jira] [Updated] (HAWQ-401) json type support

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-401:
---
Issue Type: Wish  (was: New Feature)

> json type support
> -
>
> Key: HAWQ-401
> URL: https://issues.apache.org/jira/browse/HAWQ-401
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: Core
>Reporter: Lei Chang
>Assignee: Lei Chang
> Fix For: backlog
>
>




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

[jira] [Resolved] (HAWQ-337) Support Label Based Scheduling in Libyarn and RM

[Lei Chang (JIRA)]

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

Lei Chang resolved HAWQ-337.

Resolution: Duplicate

> Support Label Based Scheduling in Libyarn and RM
> 
>
> Key: HAWQ-337
> URL: https://issues.apache.org/jira/browse/HAWQ-337
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: libyarn, Resource Manager
>Reporter: Lin Wen
>Assignee: Lei Chang
> Fix For: backlog
>
>




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

[jira] [Updated] (HAWQ-470) Add IDEA specific files to .gitignore

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-470:
---
Issue Type: Wish  (was: Task)

> Add IDEA specific files to .gitignore
> -
>
> Key: HAWQ-470
> URL: https://issues.apache.org/jira/browse/HAWQ-470
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: Build
>Affects Versions: 2.0.0-beta-incubating
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Attachments: 
> 0001-HAWQ-470.-Add-IDEA-specific-files-to-.gitignore.patch
>
>
> If IntelliJ IDEA is used to dev HAWQ, it looks quite ugly because all the 
> service files aren't ignored by git.



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

[jira] [Closed] (HAWQ-479) Upgrade JSON-C dependency from 0.6 to 0.12

[Lei Chang (JIRA)]

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

Lei Chang closed HAWQ-479.
--
Resolution: Fixed

> Upgrade JSON-C dependency from 0.6 to 0.12
> --
>
> Key: HAWQ-479
> URL: https://issues.apache.org/jira/browse/HAWQ-479
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Build
>Reporter: xin zhang
>Assignee: Lei Chang
>
> In order to support building HAWQ with GPORCA, we have to bump the JSON-C 
> version from 0.6 to 0.12.
> This requires changing the path of JSON from *json/json.h* to *json-c/json.h*.



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

[jira] [Updated] (HAWQ-565) libhdfs3's support for async IO

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-565:
---
Issue Type: Wish  (was: Improvement)

> libhdfs3's support for async IO
> ---
>
> Key: HAWQ-565
> URL: https://issues.apache.org/jira/browse/HAWQ-565
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: libhdfs
>Reporter: Glen Cao
>Assignee: Lei Chang
>
> Q1: Does libhdfs3 support async IO operations? I.e., when libhdfs3 writes 
> large files to HDFS, it doesn't need to block to wait for writes done. While 
> files are being written to HDFS, apps using libhdfs3 could do other things 
> meanwhile without using explicit multi-theading.
> Q2: Any schedule to support ORC files?



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

[jira] [Closed] (HAWQ-708) Consume latest GPORCA features up to version 1.630

[Lei Chang (JIRA)]

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

Lei Chang closed HAWQ-708.
--
Resolution: Fixed

Code has been merged

> Consume latest GPORCA features up to version 1.630
> --
>
> Key: HAWQ-708
> URL: https://issues.apache.org/jira/browse/HAWQ-708
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Optimizer
>Reporter: xin zhang
>Assignee: Amr El-Helw
>
> There are additional GPORCA features benefiting the HAWQ community, and this 
> ticket is to bump the GPORCA from version 1.627 to 1.630. Here is list of new 
> features in GPORCA:
> -- 1.628 and rename EatMalloc to EatTracker
>Better memory tracking.
> -- 1.629 to include new GUC for Join Exploration
> New GUC optimizer_join_arity_for_associativity_commutativity is added to
> control Join exploration, hence speed up optimization time [#116333899]
> For example, `set optimizer_join_arity_for_associativity_commutativity=x` 
> will
> hint at the optimizer to stop exploring join associativity and join
> commutativity transformations when an n-ary join operator has more than
> x children during optimization, pruning quite a bit of the search space.
> -- 1.630 to fix CTE Predicate pushdown
> This fix will prevent predicate pushdown with volatile function like
> random(), which caused wrong result if predicates were duplicated.



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

[jira] [Closed] (HAWQ-718) wiki of "Build and Install" for CentOS 7.x has some little issues.

[Lei Chang (JIRA)]

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

Lei Chang closed HAWQ-718.
--
Resolution: Fixed

> wiki of "Build and Install" for CentOS 7.x has some little issues.
> --
>
> Key: HAWQ-718
> URL: https://issues.apache.org/jira/browse/HAWQ-718
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Rafael Gu
>Assignee: Paul Guo
>
> Followed https://cwiki.apache.org/confluence/display/HAWQ/Build+and+Install 
> several days ago, I built and installed HAWQ on my two PCs both with CentOS 7 
> installed.  One is i7/16G/native centos 7, another is i7/8G/vmware centos 7.  
> I found some issues(both machines) as follows:
> 1. There is another lib need to be yum installed when I met some compiling 
> errors.  Sorry, I forgot the lib's name:(, but it's easy to find if you 
> recompile HAWQ on a cleaned CentOS 7.
> 2. I met "library initialization failed - unable to allocate file descriptor 
> table - out of memory ".  I cannot find suggested hardware(memory) pages, 
> looks 16G memory is too small to compile HAWQ.  I adjust vm.overcommit_memory 
> from 2 to 1(mentioned by Lei Chang) and compiling process passed:)
> 3. It's confused when I saw [# Please follow the above steps to install 
> libyarn. You may need to run "ldconfig -p " after libyarn is 
> installed.], I cannot find what's "the above steps to install libyarn".  I 
> just compiled and ldconfig the libyarn like other lib sourcecode I did, and 
> it works well.
> 4. I also met the errors as follows, when I want to run HAWQ:
> 20160429:18:15:24:071396 hawq_init:localhost:rafael-[ERROR]:-sync 
> hawq-site.xml failed.
> 20160429:18:15:24:071396 hawq_init:localhost:rafael-[ERROR]:-Set 
> default_hash_table_bucket_number failed   
> Lei Change helped me again to solve this issue by using password-less ssh.  
> No corresponding words found in the wiki document.
> Hope above descriptions helps to improve the WiKi document.



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

[jira] [Updated] (HAWQ-761) Provide brew packaging for HAWQ

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-761:
---
Issue Type: Wish  (was: Improvement)

> Provide brew packaging for HAWQ
> ---
>
> Key: HAWQ-761
> URL: https://issues.apache.org/jira/browse/HAWQ-761
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: Build
>Reporter: Roman Shaposhnik
>Assignee: Lei Chang
>
> Now that HAWQ is getting really close to rolling its first official Incubator 
> release it would be great to provide brew packaging for it so that more folks 
> can take it for a spin.
> Here's what it takes to add a formula to brew (ask on this JIRA if you have 
> further questions):
>  
> https://github.com/Homebrew/brew/blob/master/share/doc/homebrew/Formula-Cookbook.md
> I propose that for the brew packaging HAWQ is configured to use local 
> filesystem as HDFS (more correctly HCFS) and runs without YARN in a 
> standalone mode.



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

[GitHub] incubator-hawq issue #644: Remove traceflag that allows ORCA to run in multi...

[ictmalili]

Github user ictmalili commented on the issue:

https://github.com/apache/incubator-hawq/pull/644
  
@vraghavan78 what is the status of this merge?


---
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-779) support more pxf filter pushdwon

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-779:
---
Issue Type: New Feature  (was: Wish)

>  support more pxf filter pushdwon
> -
>
> Key: HAWQ-779
> URL: https://issues.apache.org/jira/browse/HAWQ-779
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: PXF
>Reporter: Devin Jia
>Assignee: Goden Yao
> Fix For: backlog
>
>
> When I use the pxf hawq, I need to read a traditional relational database 
> systems and solr by way of the external table. The project 
> :https://github.com/Pivotal-Field-Engineering/pxf-field/tree/master/jdbc-pxf-ext,
>  only "WriteAccessor ",so I developed 2 plug-ins, the projects: 
> https://github.com/inspur-insight/pxf-plugin , But these two plug-ins need to 
> modified HAWQ:
> 1. When get a list of fragment from pxf services, push down the 
> 'filterString'. modify the backend / optimizer / plan / createplan.c of 
> create_pxf_plan methods:
> segdb_work_map = map_hddata_2gp_segments (uri_str,
> total_segs, segs_participating,
> relation, ctx-> root-> parse-> jointree-> quals);
> 2. modify pxffilters.h and pxffilters.c, support TEXT types LIKE operation, 
> Date type data operator, Float type operator.
> 3. Modify org.apache.hawq.pxf.api.FilterParser.java, support the LIKE 
> operator.
> I already created a feature branch in my local ,and tested.



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

[jira] [Updated] (HAWQ-786) HAWQ supports ORC as a native storage format

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-786:
---
Issue Type: Wish  (was: New Feature)

> HAWQ supports ORC as a native storage format
> 
>
> Key: HAWQ-786
> URL: https://issues.apache.org/jira/browse/HAWQ-786
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: Storage
>Reporter: Lei Chang
>Assignee: hongwu
> Attachments: ORCdesign-v0.1-2016-06-17.pdf
>
>
> In current HAWQ, two native formats are supported: AO and parquet. Now we 
> want to support ORC. A framework to support naive c/c++ pluggable format is 
> needed to support ORC more easily. And it can also be potentially used for 
> fast external data access.



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

[jira] [Updated] (HAWQ-788) Explicitly initialize GPOPT and its dependencies

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-788:
---
Issue Type: Improvement  (was: New Feature)

> Explicitly initialize GPOPT and its dependencies
> 
>
> Key: HAWQ-788
> URL: https://issues.apache.org/jira/browse/HAWQ-788
> Project: Apache HAWQ
>  Issue Type: Improvement
>Reporter: Ivan Weng
>Assignee: Lei Chang
>




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

[jira] [Updated] (HAWQ-790) Remove CTranslatorPlStmtToDXL Deadcode

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-790:
---
Summary: Remove CTranslatorPlStmtToDXL Deadcode  (was: Remove 
CTranslatorPlStmtToDXL Deadcode [#119102697])

> Remove CTranslatorPlStmtToDXL Deadcode
> --
>
> Key: HAWQ-790
> URL: https://issues.apache.org/jira/browse/HAWQ-790
> Project: Apache HAWQ
>  Issue Type: Improvement
>Reporter: Ivan Weng
>Assignee: Lei Chang
>




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

[jira] [Updated] (HAWQ-790) Remove CTranslatorPlStmtToDXL Deadcode [#119102697]

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-790:
---
Issue Type: Improvement  (was: Task)

> Remove CTranslatorPlStmtToDXL Deadcode [#119102697]
> ---
>
> Key: HAWQ-790
> URL: https://issues.apache.org/jira/browse/HAWQ-790
> Project: Apache HAWQ
>  Issue Type: Improvement
>Reporter: Ivan Weng
>Assignee: Lei Chang
>




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

[jira] [Resolved] (HAWQ-817) Remove deprecated test cases from checkinstall-good

[Lei Chang (JIRA)]

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

Lei Chang resolved HAWQ-817.

Resolution: Fixed

> Remove deprecated test cases from checkinstall-good
> ---
>
> Key: HAWQ-817
> URL: https://issues.apache.org/jira/browse/HAWQ-817
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Core
>Reporter: Yi Jin
>Assignee: Yi Jin
>




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

[jira] [Commented] (HAWQ-833) Lack of pgcrypto.sql for the pgcrypto support

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-833:
-

Github user huor commented on the issue:

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


> Lack of pgcrypto.sql for the pgcrypto support
> -
>
> Key: HAWQ-833
> URL: https://issues.apache.org/jira/browse/HAWQ-833
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Paul Guo
>Assignee: Lei Chang
>
> Currently we use upstream postgres/pgcrypto for the pgcrypto support. The 
> version we are using just provides the sql file for the "create extension" 
> command which has not been supported on our code. We need to provide a 
> separate  pgcrypto.sql (and its corresponding uninstall sql file), just like 
> what pl/plr code does, then users could use the pgcrypto functionality as 
> before.



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

[GitHub] incubator-hawq issue #732: HAWQ-833. Lack of pgcrypto.sql for the pgcrypto s...

[huor]

Github user huor commented on the issue:

https://github.com/apache/incubator-hawq/pull/732
  
+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] [Updated] (HAWQ-831) Re-implementation for some data types of Parquet in HAWQ

[Lei Chang (JIRA)]

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

Lei Chang updated HAWQ-831:
---
Issue Type: New Feature  (was: Task)

> Re-implementation for some data types of Parquet in HAWQ
> 
>
> Key: HAWQ-831
> URL: https://issues.apache.org/jira/browse/HAWQ-831
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Storage
>Reporter: Lili Ma
>Assignee: Lei Chang
>
> Re-implement some HAWQ data type mapping to Parquet, so that HAWQ can be 
> compatible with Hive.
> 1. Currently HAWQ converts data type decimal to byte array, we can modify it 
> to fixed length byte array, so that HAWQ can be compatible with Hive.
> 2. HAWQ itself can convert the data type char to int32 instead of byte array, 
> so that the space for char storage can be saved.
> 3. To be compatible with Hive, HAWQ can change its type mapping for decimal 
> to int96, but this need discussion.



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

[jira] [Commented] (HAWQ-839) Libyarn coredump when failover to standby RM

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-839:
-

Github user yaoj2 commented on the issue:

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


> Libyarn coredump when failover to standby RM
> 
>
> Key: HAWQ-839
> URL: https://issues.apache.org/jira/browse/HAWQ-839
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: libyarn
>Reporter: Lin Wen
>Assignee: Lin Wen
>
> Start hawq with yarn mode and kill Hadoop Yarn resource manager, coredump 
> happens, the stack is below: 
> #0  0x003e054325e5 in raise () from /lib64/libc.so.6
> #1  0x003e05433dc5 in abort () from /lib64/libc.so.6
> #2  0x7f04980b1109 in libyarn::HandleYarnFailoverException (e=...)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:170
> #3  0x7f04980b3211 in libyarn::ApplicationClient::getNewApplication 
> (this=0x1f17cd0)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:215
> #4  0x7f049809d639 in libyarn::LibYarnClient::createJob (this=0x1f1e500, 
> jobName="hawq", queue="default",
> jobId="")
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClient.cpp:163
> #5  0x7f04980987b8 in createJob (client=0x1f25950, jobName=Unhandled 
> dwarf expression opcode 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:61
> #6  createJob (client=0x1f25950, jobName=Unhandled dwarf expression opcode 
> 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:180
> #7  0x008e1117 in RB2YARN_registerYARNApplication ()
> #8  0x008e31ad in RB2YARN_initializeConnection ()
> #9  0x008e358b in ResBrokerMainInternal ()
> #10 0x008e38e8 in ResBrokerMain ()
> #11 0x008dfb66 in RB_LIBYARN_start ()
> #12 0x0090ae5e in MainHandlerLoop ()
> #13 0x0090b46a in ResManagerMainServer2ndPhase ()
> #14 0x0090ba14 in ResManagerMain ()
> #15 0x0090bd71 in ResManagerProcessStartup ()
> #16 0x00767f98 in CommenceNormalOperations ()
> #17 0x00768d44 in do_reaper ()
> #18 0x0076dbed in ServerLoop ()
> #19 0x0076f73e in PostmasterMain ()
> #20 0x006c828a in main ()



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

[GitHub] incubator-hawq issue #733: HAWQ-839. Fix libyarn coredump when failover to s...

[yaoj2]

Github user yaoj2 commented on the issue:

https://github.com/apache/incubator-hawq/pull/733
  
+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-839) Libyarn coredump when failover to standby RM

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-839:
-

GitHub user linwen opened a pull request:

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

HAWQ-839. Fix libyarn coredump when failover to standby RM

Please review, Thanks! 

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

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

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

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


commit 117d669f7bbaad2a0613129f1cefa89b42310975
Author: Wen Lin 
Date:   2016-06-20T08:15:30Z

HAWQ-839. Fix libyarn coredump when failover to standby RM




> Libyarn coredump when failover to standby RM
> 
>
> Key: HAWQ-839
> URL: https://issues.apache.org/jira/browse/HAWQ-839
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: libyarn
>Reporter: Lin Wen
>Assignee: Lin Wen
>
> Start hawq with yarn mode and kill Hadoop Yarn resource manager, coredump 
> happens, the stack is below: 
> #0  0x003e054325e5 in raise () from /lib64/libc.so.6
> #1  0x003e05433dc5 in abort () from /lib64/libc.so.6
> #2  0x7f04980b1109 in libyarn::HandleYarnFailoverException (e=...)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:170
> #3  0x7f04980b3211 in libyarn::ApplicationClient::getNewApplication 
> (this=0x1f17cd0)
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/ApplicationClient.cpp:215
> #4  0x7f049809d639 in libyarn::LibYarnClient::createJob (this=0x1f1e500, 
> jobName="hawq", queue="default",
> jobId="")
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClient.cpp:163
> #5  0x7f04980987b8 in createJob (client=0x1f25950, jobName=Unhandled 
> dwarf expression opcode 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:61
> #6  createJob (client=0x1f25950, jobName=Unhandled dwarf expression opcode 
> 0xf3
> )
> at 
> /home/gpadmin/workspace/hawq/incubator-hawq/depends/libyarn/src/libyarnclient/LibYarnClientC.cpp:180
> #7  0x008e1117 in RB2YARN_registerYARNApplication ()
> #8  0x008e31ad in RB2YARN_initializeConnection ()
> #9  0x008e358b in ResBrokerMainInternal ()
> #10 0x008e38e8 in ResBrokerMain ()
> #11 0x008dfb66 in RB_LIBYARN_start ()
> #12 0x0090ae5e in MainHandlerLoop ()
> #13 0x0090b46a in ResManagerMainServer2ndPhase ()
> #14 0x0090ba14 in ResManagerMain ()
> #15 0x0090bd71 in ResManagerProcessStartup ()
> #16 0x00767f98 in CommenceNormalOperations ()
> #17 0x00768d44 in do_reaper ()
> #18 0x0076dbed in ServerLoop ()
> #19 0x0076f73e in PostmasterMain ()
> #20 0x006c828a in main ()



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