[GitHub] incubator-hawq issue #1288: HAWQ-1518. Add a UDF for showing whether the dat...

[amyrazz44]

Github user amyrazz44 commented on the issue:

https://github.com/apache/incubator-hawq/pull/1288
  
@wengyanqing @interma Pls feel free to review this pr. Thank you.


---

[GitHub] incubator-hawq pull request #1288: HAWQ-1518. Add a UDF for showing whether ...

[amyrazz44]

GitHub user amyrazz44 opened a pull request:

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

HAWQ-1518. Add a UDF for showing whether the data directory is an 
encryption zone.



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

$ git pull https://github.com/amyrazz44/incubator-hawq TDEUDF

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

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


commit 25d176bb19f049d36a97c691fb1ede5308a86ea1
Author: amyrazz44 
Date:   2017-09-14T10:18:03Z

HAWQ-1518. Add a UDF for showing whether the data directory is an 
encryption zone.




---

[jira] [Commented] (HAWQ-1528) Support read on writable external table

[Kuien Liu (JIRA)]

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

Kuien Liu commented on HAWQ-1528:
-

I guess, then comes with consistency issues, :)

> Support read on writable external table
> ---
>
> Key: HAWQ-1528
> URL: https://issues.apache.org/jira/browse/HAWQ-1528
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: External Tables
>Reporter: Ruilong Huo
>Assignee: Radar Lei
> Fix For: backlog
>
>
> It is better to support read on writable external table for convenience. BTW, 
> currently, it only support read on readable external table, and write on 
> writable external table.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HAWQ-1529) "segment resource manager" will NOT exit when postmaster died

[Kuien Liu (JIRA)]

Kuien Liu created HAWQ-1529:
---

 Summary: "segment resource manager" will NOT exit when postmaster 
died
 Key: HAWQ-1529
 URL: https://issues.apache.org/jira/browse/HAWQ-1529
 Project: Apache HAWQ
  Issue Type: Improvement
  Components: Core
Reporter: Kuien Liu
Assignee: Radar Lei


If I send SIGKILL to postmaster of segment by 'kill -9', then postmaster dies, 
BUT "segment resource manager" and "logger process" are still alive and 
flushing "WARNING" each 30s.

To my understanding, "logger process" is waiting for "segment resource 
manager", but the resource manager will not detect the alive-status of 
postmaster and continue waiting. Does it make sense? Why not quit in case of 
postmaster gone? 

The call stack of RM when postmaster is killed:
#0  0x7f19023ccab6 in poll () from /lib64/libc.so.6
#1  0x00a48c9e in processAllCommFileDescs () at rmcomm_AsyncComm.c:156
#2  0x00a8ce5e in MainHandlerLoop_RMSEG () at 
resourcemanager_RMSEG.c:166
#3  0x00a8cba3 in ResManagerMainSegment2ndPhase () at 
resourcemanager_RMSEG.c:71
#4  0x00a8d966 in ResManagerMain (argc=0x3, argv=0x7fffa018b890) at 
resourcemanager.c:346
#5  0x00a8db45 in ResManagerProcessStartup () at resourcemanager.c:411
#6  0x00899b89 in CommenceNormalOperations () at postmaster.c:3673
#7  0x0089a562 in do_reaper () at postmaster.c:4021
#8  0x008969bb in ServerLoop () at postmaster.c:2136
#9  0x00895a78 in PostmasterMain (argc=0xc, argv=0x229a730) at 
postmaster.c:1454
#10 0x007b185d in main (argc=0xc, argv=0x229a730) at main.c:226
#11 0x7f190231e994 in __libc_start_main () from /lib64/libc.so.6
#12 0x004bde89 in _start ()




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)