[jira] [Commented] (HAWQ-593) Function crashes with PANIC in planning stage related to gp_cte_sharing

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-593:
-

GitHub user xinzweb opened a pull request:

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

HAWQ-593: Port cdbmutate fix from GPDB4

SHA is ab19a2fdd16f1eb119ba326575bbbaa5602d5a52

Signed-off-by: Venkatesh Raghavan 

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

$ git pull https://github.com/xinzweb/incubator-hawq 
port_cdbmutate_113027835

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

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


commit b409c482f225044294d5c8137a46a4976345e2bc
Author: Xin Zhang 
Date:   2016-03-25T21:04:29Z

Port cdbmutate fix from GPDB4

SHA is ab19a2fdd16f1eb119ba326575bbbaa5602d5a52

Signed-off-by: Venkatesh Raghavan 




> Function crashes with PANIC in planning stage related to gp_cte_sharing
> ---
>
> Key: HAWQ-593
> URL: https://issues.apache.org/jira/browse/HAWQ-593
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Optimizer
>Reporter: xin zhang
>Assignee: Amr El-Helw
>
> Small repro:
> {code}
> set optimizer=off;
> set gp_cte_sharing=on=on;
> create table t (c int);
> insert into t values (2);
> explain 
> with cte0 (e) as (values (0), (1)) 
> select c, count(distinct d) disc_d
> from (
> select c, d
> from (
>   select 
> case 
>   when t.c in (select e from cte0) then 'a'
>   when t.c not in (select e from cte0) then 'b'
> end as d,
> c
>   from t, cte0
> ) A 
> group by c, d
> ) B
> group by c;
> {code}



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

[jira] [Comment Edited] (HAWQ-358) Installcheck good failures in hawq-dev environment

[xin zhang (JIRA)]

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

xin zhang edited comment on HAWQ-358 at 3/25/16 6:12 PM:
-

At this moment, only two tests failed on OSX (not on Linux)

{code}
test exttab1  ... FAILED (11.18 sec)
test hcatalog_lookup  ... FAILED (0.71 sec) (test process exited with 
unexpected exit code 2, but was expected exit code 0)
{code}

{code}
===
 2 of 56 tests failed.
===
{code}

The regression.diffs is:
{code}
*** ./expected/exttab1_optimizer.out2016-03-25 10:23:17.0 -0700
--- ./results/exttab1.out   2016-03-25 10:23:17.0 -0700
***
*** 610,617 
  --drop foreign table ext; -- should fail (wrong object)
  --drop external table ext;
  --
!   r_name   
!  MIDDLE EAST  
  --
  --
  --
--- 599,606 
  --drop foreign table ext; -- should fail (wrong object)
  --drop external table ext;
  --
!   x   
!  Okay, gpfdist version "2.0.0.0_beta build dev" is running on localhost:7070.
  --
  --
  --
***
*** 673,680 
  -- in between runs, so we don't check for count(*), and instead check for 
distinct.
  -- negative
  -- positive
! ---
  --
  ERROR:  location uri "gpfdist://localhost:7070/wet.out" appears more than once
  ERROR:  the ON segment syntax for writableexternal tables is 
deprecated
  ERROR:  the file protocol for external tables is deprecated
--- 662,670 
  -- in between runs, so we don't check for count(*), and instead check for 
distinct.
  -- negative
  -- positive
! -- start_ignore
  --
+ --
  ERROR:  location uri "gpfdist://localhost:7070/wet.out" appears more than once
  ERROR:  the ON segment syntax for writable external tables is deprecated
  ERROR:  the file protocol for external tables is deprecated
***
*** 690,720 
  create writable external table wet_pos3(like wet_pos2) 
location('gpfdist://localhost:7070/wet.out') format 'text' distributed by(a,b);
  create writable external table wet_region(like reg_region) 
location('gpfdist://localhost:7070/wet_region.out') format 'text';
  create writable external web table wet_pos5(a text, b text) execute 'some 
command' on segment 0 format 'text';
  select * from wet_pos1;
  (1 row)
  
! GP_IGNORE:-- start_ignore
! GP_IGNORE:select * from gpfdist_status;
! GP_IGNORE: x  
   
! 
GP_IGNORE:--
! GP_IGNORE: Okay, gpfdist version "1.3.0.0 build dev" is running on 
localhost:7070.
! GP_IGNORE:(1 row)
! GP_IGNORE:
! GP_IGNORE:select * from gpfdist_stop;
! GP_IGNORE:  x  
! GP_IGNORE:-
! GP_IGNORE: stopping...
! GP_IGNORE:(1 row)
! GP_IGNORE:
! GP_IGNORE:select * from gpfdist_status;
! GP_IGNORE:  x   
! GP_IGNORE:--
! GP_IGNORE: Error: gpfdist is not running (reason: socket error)
! GP_IGNORE: Exit: 1
! GP_IGNORE: 
! GP_IGNORE:(3 rows)
! GP_IGNORE:
! GP_IGNORE:-- end_ignore
  --
  -- get an error for missing gpfdist
  --
--- 680,704 
  create writable external table wet_pos3(like wet_pos2) 
location('gpfdist://localhost:7070/wet.out') format 'text' distributed by(a,b);
  create writable external table wet_region(like reg_region) 
location('gpfdist://localhost:7070/wet_region.out') format 'text';
  create writable external web table wet_pos5(a text, b text) execute 'some 
command' on segment 0 format 'text';
+ select * from gpfdist_status;
  select * from wet_pos1;
  (1 row)
  
! select * from gpfdist_stop;
!   x  
! -
!  stopping...
! (1 row)
! 
! select * from gpfdist_status;
!   x   
! --
!  
!  Error: gpfdist is not running (reason: socket error)
!  Exit: 1
! (3 rows)
! 
! -- end_ignore
  --
  -- get an error for missing gpfdist
  --

==

*** ./expected/hcatalog_lookup.out  2016-03-25 10:23:55.0 -0700
--- ./results/hcatalog_lookup.out   2016-03-25 10:23:55.0 -0700
***
*** 13,22 
  -- enable GUC
  SET hcatalog_enable = true;
  SELECT * FROM pxf_get_item_fields('Hive', '*abc*abc*');
!  path | itemname | 

[jira] [Commented] (HAWQ-404) Add sort during INSERT of append only row oriented partition tables

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-404:
-

Github user vraghavan78 commented on the pull request:

https://github.com/apache/incubator-hawq/pull/511#issuecomment-20138
  
+1


> Add sort during INSERT of append only row oriented partition tables
> ---
>
> Key: HAWQ-404
> URL: https://issues.apache.org/jira/browse/HAWQ-404
> Project: Apache HAWQ
>  Issue Type: Improvement
>Reporter: Haisheng Yuan
>Assignee: Lei Chang
>




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

[jira] [Comment Edited] (HAWQ-358) Installcheck good failures in hawq-dev environment

[xin zhang (JIRA)]

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

xin zhang edited comment on HAWQ-358 at 3/25/16 5:34 PM:
-

At this moment, only two tests failed:

{code}
test exttab1  ... FAILED (11.18 sec)
test hcatalog_lookup  ... FAILED (0.71 sec) (test process exited with 
unexpected exit code 2, but was expected exit code 0)
{code}

{code}
===
 2 of 56 tests failed.
===
{code}

The regression.diffs is:
{code}
*** ./expected/exttab1_optimizer.out2016-03-25 10:23:17.0 -0700
--- ./results/exttab1.out   2016-03-25 10:23:17.0 -0700
***
*** 610,617 
  --drop foreign table ext; -- should fail (wrong object)
  --drop external table ext;
  --
!   r_name   
!  MIDDLE EAST  
  --
  --
  --
--- 599,606 
  --drop foreign table ext; -- should fail (wrong object)
  --drop external table ext;
  --
!   x   
!  Okay, gpfdist version "2.0.0.0_beta build dev" is running on localhost:7070.
  --
  --
  --
***
*** 673,680 
  -- in between runs, so we don't check for count(*), and instead check for 
distinct.
  -- negative
  -- positive
! ---
  --
  ERROR:  location uri "gpfdist://localhost:7070/wet.out" appears more than once
  ERROR:  the ON segment syntax for writableexternal tables is 
deprecated
  ERROR:  the file protocol for external tables is deprecated
--- 662,670 
  -- in between runs, so we don't check for count(*), and instead check for 
distinct.
  -- negative
  -- positive
! -- start_ignore
  --
+ --
  ERROR:  location uri "gpfdist://localhost:7070/wet.out" appears more than once
  ERROR:  the ON segment syntax for writable external tables is deprecated
  ERROR:  the file protocol for external tables is deprecated
***
*** 690,720 
  create writable external table wet_pos3(like wet_pos2) 
location('gpfdist://localhost:7070/wet.out') format 'text' distributed by(a,b);
  create writable external table wet_region(like reg_region) 
location('gpfdist://localhost:7070/wet_region.out') format 'text';
  create writable external web table wet_pos5(a text, b text) execute 'some 
command' on segment 0 format 'text';
  select * from wet_pos1;
  (1 row)
  
! GP_IGNORE:-- start_ignore
! GP_IGNORE:select * from gpfdist_status;
! GP_IGNORE: x  
   
! 
GP_IGNORE:--
! GP_IGNORE: Okay, gpfdist version "1.3.0.0 build dev" is running on 
localhost:7070.
! GP_IGNORE:(1 row)
! GP_IGNORE:
! GP_IGNORE:select * from gpfdist_stop;
! GP_IGNORE:  x  
! GP_IGNORE:-
! GP_IGNORE: stopping...
! GP_IGNORE:(1 row)
! GP_IGNORE:
! GP_IGNORE:select * from gpfdist_status;
! GP_IGNORE:  x   
! GP_IGNORE:--
! GP_IGNORE: Error: gpfdist is not running (reason: socket error)
! GP_IGNORE: Exit: 1
! GP_IGNORE: 
! GP_IGNORE:(3 rows)
! GP_IGNORE:
! GP_IGNORE:-- end_ignore
  --
  -- get an error for missing gpfdist
  --
--- 680,704 
  create writable external table wet_pos3(like wet_pos2) 
location('gpfdist://localhost:7070/wet.out') format 'text' distributed by(a,b);
  create writable external table wet_region(like reg_region) 
location('gpfdist://localhost:7070/wet_region.out') format 'text';
  create writable external web table wet_pos5(a text, b text) execute 'some 
command' on segment 0 format 'text';
+ select * from gpfdist_status;
  select * from wet_pos1;
  (1 row)
  
! select * from gpfdist_stop;
!   x  
! -
!  stopping...
! (1 row)
! 
! select * from gpfdist_status;
!   x   
! --
!  
!  Error: gpfdist is not running (reason: socket error)
!  Exit: 1
! (3 rows)
! 
! -- end_ignore
  --
  -- get an error for missing gpfdist
  --

==

*** ./expected/hcatalog_lookup.out  2016-03-25 10:23:55.0 -0700
--- ./results/hcatalog_lookup.out   2016-03-25 10:23:55.0 -0700
***
*** 13,22 
  -- enable GUC
  SET hcatalog_enable = true;
  SELECT * FROM pxf_get_item_fields('Hive', '*abc*abc*');
!  path | itemname | fieldname | fieldtype 

[jira] [Commented] (HAWQ-404) Add sort during INSERT of append only row oriented partition tables

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-404:
-

Github user xinzweb commented on the pull request:

https://github.com/apache/incubator-hawq/pull/511#issuecomment-201377646
  
@vraghavan78 @changleicn Please take a look. Thanks.


> Add sort during INSERT of append only row oriented partition tables
> ---
>
> Key: HAWQ-404
> URL: https://issues.apache.org/jira/browse/HAWQ-404
> Project: Apache HAWQ
>  Issue Type: Improvement
>Reporter: Haisheng Yuan
>Assignee: Lei Chang
>




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

[jira] [Commented] (HAWQ-572) Improve code coverage for dispatcher: fail_qe_after_connection & fail_qe_when_do_query & fail_qe_when_begin_parquet_scan

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-572:
-

GitHub user wcl14 opened a pull request:

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

HAWQ-572. Add fault injection in parquet_getnext().

HAWQ-572. Add fault injection in parquet_getnext().

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

$ git pull https://github.com/wcl14/incubator-hawq HAWQ-572

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

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


commit 62d42d3108fb48a23941c3858615eb6a070f62be
Author: Chunling Wang 
Date:   2016-03-25T10:23:44Z

HAWQ-572. Add fault injection in parquet_getnext().




> Improve code coverage for dispatcher: fail_qe_after_connection & 
> fail_qe_when_do_query & fail_qe_when_begin_parquet_scan
> 
>
> Key: HAWQ-572
> URL: https://issues.apache.org/jira/browse/HAWQ-572
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Dispatcher
>Reporter: Chunling Wang
>Assignee: Lei Chang
>
> Add those fault injections:
> 1. fail_qe_after_connection 
> 2. fail_qe_when_do_query 
> 3. fail_qe_when_begin_parquet_scan
> And add test cases.



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

[jira] [Commented] (HAWQ-590) Remove Dead Codes in resourcepool.c and requesthandler_ddl.c

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-590:
-

Github user jiny2 commented on the pull request:

https://github.com/apache/incubator-hawq/pull/508#issuecomment-201231705
  
LGTM +1


> Remove Dead Codes in resourcepool.c and requesthandler_ddl.c
> 
>
> Key: HAWQ-590
> URL: https://issues.apache.org/jira/browse/HAWQ-590
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Lin Wen
>Assignee: Lin Wen
>




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

[jira] [Updated] (HAWQ-592) QD fails when connects to QE again in executormgr_allocate_any_executor()

[Chunling Wang (JIRA)]

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

Chunling Wang updated HAWQ-592:
---
Description: 
We first run a query to get some QEs. Then we kill one and run "set 
log_min_messages=DEBUG1" to let QD get executormgr_allocate_any_executor(). We 
find QD failed.
1. Run query to get some QEs.
{code}
dispatch=# select count(*) from test_dispatch as t1, test_dispatch as t2, 
test_dispatch as t3 where t1.id *2 = t2.id and t1.id < t3.id;
 count
---
  3725
(1 row)
{code}
{code}
$ ps -ef|grep postgres
  501 12817 1   0  4:41下午 ?? 0:00.36 /usr/local/hawq/bin/postgres 
-D /Users/wangchunling/hawq-data-directory/masterdd -i -M master -p 5432 
--silent-mode=true
  501 12818 12817   0  4:41下午 ?? 0:00.01 postgres: port  5432, master 
logger process
  501 12821 12817   0  4:41下午 ?? 0:00.00 postgres: port  5432, stats 
collector process
  501 12822 12817   0  4:41下午 ?? 0:00.03 postgres: port  5432, writer 
process
  501 12823 12817   0  4:41下午 ?? 0:00.00 postgres: port  5432, 
checkpoint process
  501 12824 12817   0  4:41下午 ?? 0:00.00 postgres: port  5432, 
seqserver process
  501 12825 12817   0  4:41下午 ?? 0:00.00 postgres: port  5432, WAL Send 
Server process
  501 12826 12817   0  4:41下午 ?? 0:00.00 postgres: port  5432, DFS 
Metadata Cache process
  501 12827 12817   0  4:41下午 ?? 0:00.16 postgres: port  5432, master 
resource manager
  501 12844 1   0  4:41下午 ?? 0:00.57 /usr/local/hawq/bin/postgres 
-D /Users/wangchunling/hawq-data-directory/segmentdd -i -M segment -p 4 
--silent-mode=true
  501 12845 12844   0  4:41下午 ?? 0:00.01 postgres: port 4, logger 
process
  501 12856 12862   0  4:42下午 ?? 0:00.05 postgres: port  5432, 
wangchunling dispatch [local] con13 cmd10 idle [local]
  501 12872 12844   0  4:42下午 ?? 0:00.00 postgres: port 4, stats 
collector process
  501 12873 12844   0  4:42下午 ?? 0:00.01 postgres: port 4, writer 
process
  501 12874 12844   0  4:42下午 ?? 0:00.00 postgres: port 4, 
checkpoint process
  501 12875 12844   0  4:42下午 ?? 0:00.03 postgres: port 4, segment 
resource manager
{code}
2. Kill -9 some QE and wait segment up.
{code}
$ ps -ef|grep postgres
  501 12817 1   0  4:41下午 ?? 0:00.91 /usr/local/hawq/bin/postgres 
-D /Users/wangchunling/hawq-data-directory/masterdd -i -M master -p 5432 
--silent-mode=true
  501 12818 12817   0  4:41下午 ?? 0:00.05 postgres: port  5432, master 
logger process
  501 12844 1   0  4:41下午 ?? 0:01.52 /usr/local/hawq/bin/postgres 
-D /Users/wangchunling/hawq-data-directory/segmentdd -i -M segment -p 4 
--silent-mode=true
  501 12845 12844   0  4:41下午 ?? 0:00.04 postgres: port 4, logger 
process
  501 12872 12844   0  4:42下午 ?? 0:00.02 postgres: port 4, stats 
collector process
  501 12873 12844   0  4:42下午 ?? 0:00.19 postgres: port 4, writer 
process
  501 12874 12844   0  4:42下午 ?? 0:00.03 postgres: port 4, 
checkpoint process
  501 12875 12844   0  4:42下午 ?? 0:00.41 postgres: port 4, segment 
resource manager
  501 12932 12817   0  4:52下午 ?? 0:00.00 postgres: port  5432, stats 
collector process
  501 12933 12817   0  4:52下午 ?? 0:00.01 postgres: port  5432, writer 
process
  501 12934 12817   0  4:52下午 ?? 0:00.00 postgres: port  5432, 
checkpoint process
  501 12935 12817   0  4:52下午 ?? 0:00.00 postgres: port  5432, 
seqserver process
  501 12936 12817   0  4:52下午 ?? 0:00.00 postgres: port  5432, WAL Send 
Server process
  501 12937 12817   0  4:52下午 ?? 0:00.00 postgres: port  5432, DFS 
Metadata Cache process
  501 12938 12817   0  4:52下午 ?? 0:00.04 postgres: port  5432, master 
resource manager
  501 12952 12817   0  4:53下午 ?? 0:00.00 postgres: port  5432, 
wangchunling dispatch [local] con30 idle [local]
{code}
{code}
dispatch=# select * from gp_segment_configuration;
 registration_order | role | status | port  |  hostname   | 
  address   |description
+--++---+-+-+
  0 | m| u  |  5432 | ChunlingdeMacBook-Pro.local | 
ChunlingdeMacBook-Pro.local |
  1 | p| d  | 4 | localhost   | 
127.0.0.1   | resource manager process was reset
(2 rows)

dispatch=# select * from gp_segment_configuration;
 registration_order | role | status | port  |  hostname   | 
  address   | description
+--++---+-+-+-
  0 | m| u  |  5432 | 

[jira] [Commented] (HAWQ-591) Explain analyze should not gather QE execution detail when QE runtime error has been caught by QD

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-591:
-

Github user ztao1987 commented on the pull request:

https://github.com/apache/incubator-hawq/pull/509#issuecomment-201213671
  
+1



> Explain analyze should not gather QE execution detail when QE runtime error 
> has been caught by QD
> -
>
> Key: HAWQ-591
> URL: https://issues.apache.org/jira/browse/HAWQ-591
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Dispatcher
>Reporter: Lili Ma
>Assignee: Lei Chang
>
> In function cdbexplain_recvExecStats, it will gather QE runtime statistics, 
> and will elog ERROR under some cases. But when QE gets error or is killed, 
> the error information will be caught by dispatcher, and the error under 
> explain analyze will be marked as 'NOTICE' instead of 'DEBUG', if we enter 
> into function cdbexplain_recvExecStats, the elog error will cover and shield 
> the actual information from QE. 
> So if dispatcher has caught QE error, we should not enter 
> cdbexplain_recvExecStats.



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

[jira] [Commented] (HAWQ-591) Explain analyze should not gather QE execution detail when QE runtime error has been caught by QD

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HAWQ-591:
-

GitHub user ictmalili opened a pull request:

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

HAWQ-591. Explain analyze doesn't enter function cdbexplain_recvExecS…

…tats after QD finding QE error

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

$ git pull https://github.com/ictmalili/incubator-hawq HAWQ-591

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

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


commit 99aed92cc6b54a317e27dbcb800d6c99d472fa18
Author: Lili Ma 
Date:   2016-03-25T09:08:24Z

HAWQ-591. Explain analyze doesn't enter function cdbexplain_recvExecStats 
after QD finding QE error




> Explain analyze should not gather QE execution detail when QE runtime error 
> has been caught by QD
> -
>
> Key: HAWQ-591
> URL: https://issues.apache.org/jira/browse/HAWQ-591
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Dispatcher
>Reporter: Lili Ma
>Assignee: Lei Chang
>
> In function cdbexplain_recvExecStats, it will gather QE runtime statistics, 
> and will elog ERROR under some cases. But when QE gets error or is killed, 
> the error information will be caught by dispatcher, and the error under 
> explain analyze will be marked as 'NOTICE' instead of 'DEBUG', if we enter 
> into function cdbexplain_recvExecStats, the elog error will cover and shield 
> the actual information from QE. 
> So if dispatcher has caught QE error, we should not enter 
> cdbexplain_recvExecStats.



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

[jira] [Created] (HAWQ-592) QD fails when connects to QE again in executormgr_allocate_any_executor()

[Chunling Wang (JIRA)]

Chunling Wang created HAWQ-592:
--

 Summary: QD fails when connects to QE again in 
executormgr_allocate_any_executor()
 Key: HAWQ-592
 URL: https://issues.apache.org/jira/browse/HAWQ-592
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Dispatcher
Reporter: Chunling Wang
Assignee: Lei Chang


We first run a query to get some QEs. Then we kill one and run "set 
log_min_messages=DEBUG1" to let QD get executormgr_allocate_any_executor(). We 
find QD failed.



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

[jira] [Updated] (HAWQ-592) QD fails when connects to QE again in executormgr_allocate_any_executor()

[Chunling Wang (JIRA)]

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

Chunling Wang updated HAWQ-592:
---
Affects Version/s: 2.0.0

> QD fails when connects to QE again in executormgr_allocate_any_executor()
> -
>
> Key: HAWQ-592
> URL: https://issues.apache.org/jira/browse/HAWQ-592
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Dispatcher
>Affects Versions: 2.0.0
>Reporter: Chunling Wang
>Assignee: Lei Chang
>
> We first run a query to get some QEs. Then we kill one and run "set 
> log_min_messages=DEBUG1" to let QD get executormgr_allocate_any_executor(). 
> We find QD failed.



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

[jira] [Created] (HAWQ-591) Explain analyze should not gather QE execution detail when QE runtime error has been caught by QD

[Lili Ma (JIRA)]

Lili Ma created HAWQ-591:


 Summary: Explain analyze should not gather QE execution detail 
when QE runtime error has been caught by QD
 Key: HAWQ-591
 URL: https://issues.apache.org/jira/browse/HAWQ-591
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Dispatcher
Reporter: Lili Ma
Assignee: Lei Chang


In function cdbexplain_recvExecStats, it will gather QE runtime statistics, and 
will elog ERROR under some cases. But when QE gets error or is killed, the 
error information will be caught by dispatcher, and the error under explain 
analyze will be marked as 'NOTICE' instead of 'DEBUG', if we enter into 
function cdbexplain_recvExecStats, the elog error will cover and shield the 
actual information from QE. 
So if dispatcher has caught QE error, we should not enter 
cdbexplain_recvExecStats.



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

[jira] [Assigned] (HAWQ-590) Remove Dead Codes in resourcepool.c and requesthandler_ddl.c

[Lin Wen (JIRA)]

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

Lin Wen reassigned HAWQ-590:


Assignee: Lin Wen  (was: Lei Chang)

> Remove Dead Codes in resourcepool.c and requesthandler_ddl.c
> 
>
> Key: HAWQ-590
> URL: https://issues.apache.org/jira/browse/HAWQ-590
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Lin Wen
>Assignee: Lin Wen
>




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

[jira] [Created] (HAWQ-590) Remove Dead Codes in resourcepool.c and requesthandler_ddl.c

[Lin Wen (JIRA)]

Lin Wen created HAWQ-590:


 Summary: Remove Dead Codes in resourcepool.c and 
requesthandler_ddl.c
 Key: HAWQ-590
 URL: https://issues.apache.org/jira/browse/HAWQ-590
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Resource Manager
Reporter: Lin Wen
Assignee: Lei Chang






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