[jira] [Commented] (HAWQ-930) HAWQ RM can not work
[ https://issues.apache.org/jira/browse/HAWQ-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381801#comment-15381801 ] Biao Wu commented on HAWQ-930: -- No query is running before run "hawq restart cluster". No postgres tasks running. > HAWQ RM can not work > > > Key: HAWQ-930 > URL: https://issues.apache.org/jira/browse/HAWQ-930 > Project: Apache HAWQ > Issue Type: Bug > Components: Core >Affects Versions: 2.0.1.0-incubating >Reporter: Biao Wu >Assignee: Lei Chang > > The HAWQ Version is "HAWQ version 2.0.1.0 build dev". > segment number:17 > Run `hawq restart cluster`, > the pg_log: > 2016-07-18 14:04:42.799428 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 151",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:43.799498 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 152",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:44.799569 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 153",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:45.799639 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 154",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:46.799709 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 155",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:47.799780 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 156",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:48.799850 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 157",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:49.799918 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 158",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:50.799988 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 159",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:51.800056 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 160",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:52.800126 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 161",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:53.800195 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 162",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:54.800263 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 163",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:55.800331 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 164",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:56.800399 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 165",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:57.800466 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 166",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:58.800535 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 167",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:59.800602 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 168",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:00.800669 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 169",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:01.800736 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 170",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:02.800803 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 171",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:03.800870 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 172",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:04.800938 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 173",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:05.801004 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 174",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:06.801073 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 175",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:07.801132 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 176",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:08.801224 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 177",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:09.8012
[jira] [Commented] (HAWQ-930) HAWQ RM can not work
[ https://issues.apache.org/jira/browse/HAWQ-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381797#comment-15381797 ] Lin Wen commented on HAWQ-930: -- Hi, HAWQ RM log is also in this log file. Before run "hawq restart cluster", is there any running query? Would you please run "ps -ef | grep postgres" to check it before and after run "hawq restart cluster"? Thanks! > HAWQ RM can not work > > > Key: HAWQ-930 > URL: https://issues.apache.org/jira/browse/HAWQ-930 > Project: Apache HAWQ > Issue Type: Bug > Components: Core >Affects Versions: 2.0.1.0-incubating >Reporter: Biao Wu >Assignee: Lei Chang > > The HAWQ Version is "HAWQ version 2.0.1.0 build dev". > segment number:17 > Run `hawq restart cluster`, > the pg_log: > 2016-07-18 14:04:42.799428 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 151",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:43.799498 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 152",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:44.799569 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 153",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:45.799639 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 154",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:46.799709 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 155",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:47.799780 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 156",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:48.799850 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 157",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:49.799918 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 158",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:50.799988 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 159",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:51.800056 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 160",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:52.800126 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 161",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:53.800195 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 162",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:54.800263 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 163",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:55.800331 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 164",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:56.800399 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 165",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:57.800466 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 166",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:58.800535 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 167",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:59.800602 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 168",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:00.800669 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 169",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:01.800736 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 170",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:02.800803 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 171",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:03.800870 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 172",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:04.800938 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 173",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:05.801004 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 174",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:06.801073 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 175",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:07.801132 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 176",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:08.801224 > CST,,,p136927,
[jira] [Updated] (HAWQ-930) HAWQ RM can not work
[ https://issues.apache.org/jira/browse/HAWQ-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Biao Wu updated HAWQ-930: - Affects Version/s: 2.0.1.0-incubating > HAWQ RM can not work > > > Key: HAWQ-930 > URL: https://issues.apache.org/jira/browse/HAWQ-930 > Project: Apache HAWQ > Issue Type: Bug > Components: Core >Affects Versions: 2.0.1.0-incubating >Reporter: Biao Wu >Assignee: Lei Chang > > The HAWQ Version is "HAWQ version 2.0.1.0 build dev". > segment number:17 > Run `hawq restart cluster`, > the pg_log: > 2016-07-18 14:04:42.799428 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 151",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:43.799498 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 152",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:44.799569 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 153",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:45.799639 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 154",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:46.799709 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 155",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:47.799780 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 156",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:48.799850 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 157",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:49.799918 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 158",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:50.799988 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 159",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:51.800056 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 160",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:52.800126 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 161",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:53.800195 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 162",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:54.800263 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 163",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:55.800331 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 164",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:56.800399 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 165",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:57.800466 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 166",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:58.800535 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 167",,,0,,"resourcemanager.c",421, > 2016-07-18 14:04:59.800602 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 168",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:00.800669 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 169",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:01.800736 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 170",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:02.800803 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 171",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:03.800870 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 172",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:04.800938 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 173",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:05.801004 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 174",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:06.801073 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 175",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:07.801132 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 176",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:08.801224 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 177",,,0,,"resourcemanager.c",421, > 2016-07-18 14:05:09.801294 > CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ > RM 178",
[jira] [Created] (HAWQ-930) HAWQ RM can not work
Biao Wu created HAWQ-930: Summary: HAWQ RM can not work Key: HAWQ-930 URL: https://issues.apache.org/jira/browse/HAWQ-930 Project: Apache HAWQ Issue Type: Bug Components: Core Reporter: Biao Wu Assignee: Lei Chang The HAWQ Version is "HAWQ version 2.0.1.0 build dev". segment number:17 Run `hawq restart cluster`, the pg_log: 2016-07-18 14:04:42.799428 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 151",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:43.799498 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 152",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:44.799569 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 153",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:45.799639 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 154",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:46.799709 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 155",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:47.799780 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 156",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:48.799850 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 157",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:49.799918 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 158",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:50.799988 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 159",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:51.800056 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 160",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:52.800126 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 161",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:53.800195 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 162",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:54.800263 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 163",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:55.800331 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 164",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:56.800399 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 165",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:57.800466 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 166",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:58.800535 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 167",,,0,,"resourcemanager.c",421, 2016-07-18 14:04:59.800602 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 168",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:00.800669 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 169",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:01.800736 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 170",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:02.800803 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 171",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:03.800870 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 172",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:04.800938 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 173",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:05.801004 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 174",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:06.801073 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 175",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:07.801132 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 176",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:08.801224 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 177",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:09.801294 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 178",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:10.801367 CST,,,p136927,th-17368286400,,,seg-1,"LOG","0","Wait for HAWQ RM 179",,,0,,"resourcemanager.c",421, 2016-07-18 14:05:10.808694 CST,,,p136927,th-17368286400,,,seg-1,"FATAL","XX000","HAWQ RM can not work. Please check HAWQ RM log. (resourcemanager.c:433)",,,0,,"resourcemanager.c",433,"Stack trace:
[jira] [Commented] (HAWQ-896) Add feature test for create table with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381758#comment-15381758 ] ASF GitHub Bot commented on HAWQ-896: - Github user jiny2 closed the pull request at: https://github.com/apache/incubator-hawq/pull/798 > Add feature test for create table with new test framework > - > > Key: HAWQ-896 > URL: https://issues.apache.org/jira/browse/HAWQ-896 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > Fix For: 2.0.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #798: HAWQ-896. Add feature test for create tabl...
Github user jiny2 closed the pull request at: https://github.com/apache/incubator-hawq/pull/798 --- 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-896) Add feature test for create table with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381739#comment-15381739 ] ASF GitHub Bot commented on HAWQ-896: - Github user linwen commented on the issue: https://github.com/apache/incubator-hawq/pull/798 +1 > Add feature test for create table with new test framework > - > > Key: HAWQ-896 > URL: https://issues.apache.org/jira/browse/HAWQ-896 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > Fix For: 2.0.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #798: HAWQ-896. Add feature test for create table with ...
Github user yaoj2 commented on the issue: https://github.com/apache/incubator-hawq/pull/798 LGTM --- 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-896) Add feature test for create table with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381740#comment-15381740 ] ASF GitHub Bot commented on HAWQ-896: - Github user yaoj2 commented on the issue: https://github.com/apache/incubator-hawq/pull/798 LGTM > Add feature test for create table with new test framework > - > > Key: HAWQ-896 > URL: https://issues.apache.org/jira/browse/HAWQ-896 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > Fix For: 2.0.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-896) Add feature test for create table with new test framework
[ https://issues.apache.org/jira/browse/HAWQ-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381737#comment-15381737 ] ASF GitHub Bot commented on HAWQ-896: - GitHub user jiny2 opened a pull request: https://github.com/apache/incubator-hawq/pull/798 HAWQ-896. Add feature test for create table with new test framework You can merge this pull request into a Git repository by running: $ git pull https://github.com/jiny2/incubator-hawq HAWQ-896 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/798.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 #798 commit a79e1d72aa9b5f0c611125975245b9b5d12fd5ff Author: YI JIN Date: 2016-07-18T05:26:37Z HAWQ-896. Add feature test for create table with new test framework > Add feature test for create table with new test framework > - > > Key: HAWQ-896 > URL: https://issues.apache.org/jira/browse/HAWQ-896 > Project: Apache HAWQ > Issue Type: Sub-task > Components: Tests >Reporter: Lin Wen >Assignee: Lin Wen > Fix For: 2.0.1.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #798: HAWQ-896. Add feature test for create table with ...
Github user linwen commented on the issue: https://github.com/apache/incubator-hawq/pull/798 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-hawq pull request #798: HAWQ-896. Add feature test for create tabl...
GitHub user jiny2 opened a pull request: https://github.com/apache/incubator-hawq/pull/798 HAWQ-896. Add feature test for create table with new test framework You can merge this pull request into a Git repository by running: $ git pull https://github.com/jiny2/incubator-hawq HAWQ-896 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/798.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 #798 commit a79e1d72aa9b5f0c611125975245b9b5d12fd5ff Author: YI JIN Date: 2016-07-18T05:26:37Z HAWQ-896. Add feature test for create table with new test framework --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (HAWQ-256) Integrate Security with Apache Ranger
[ https://issues.apache.org/jira/browse/HAWQ-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381729#comment-15381729 ] Don Bosco Durai commented on HAWQ-256: -- [~hubertzhang], thanks. The JDBC call should suffice for lookup. Ranger only supports one set of users and it is generally what is supported by Hadoop. The source is either AD/LDAP or linux users. In the case of Hive, if Ranger is used, then Hive's internal users or roles are not used, instead Hadoop Common is used to get users and groups. This keeps the users and groups consistent across all components. I would prefer the same behavior for HAWQ. But for any reason HAWQ needs to support it's own users/groups, then they need to be populated in Ranger also. Since Ranger doesn't have namespace for users, it can't do conflict resolution. So we will have to do what you suggest. It would be good if we defer it and see if users really needs it? Because, users using Ranger prefer uniform user and groups. Thanks > Integrate Security with Apache Ranger > - > > Key: HAWQ-256 > URL: https://issues.apache.org/jira/browse/HAWQ-256 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF, Security >Reporter: Michael Andre Pearce (IG) >Assignee: Lili Ma > Fix For: backlog > > > Integrate security with Apache Ranger for a unified Hadoop security solution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HAWQ-256) Integrate Security with Apache Ranger
[ https://issues.apache.org/jira/browse/HAWQ-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381645#comment-15381645 ] Hubert Zhang edited comment on HAWQ-256 at 7/18/16 2:48 AM: [~bosco], HAWQ already support JDBC and to lookup for database list and schema list in HAWQ, use the following two commands: For schema list: "select nspname from pg_namespace;" For database list: "\l" I have one more question. How do ranger handle the problem of user names maybe the same in different components. For example user "hubert" may both appear in linux system, HIVE and HAWQ, Do we add a prefix like HIVE.hubert, HAWQ.hubert in RangerPolicyDB? Thanks was (Author: hubertzhang): Don, HAWQ already support JDBC and to lookup for database list and schema list in HAWQ, use the following two commands: For schema list: "select nspname from pg_namespace;" For database list: "\l" I have one more question. How do ranger handle the problem of user names maybe the same in different components. For example user "hubert" may both appear in linux system, HIVE and HAWQ, Do we add a prefix like HIVE.hubert, HAWQ.hubert in RangerPolicyDB? Thanks > Integrate Security with Apache Ranger > - > > Key: HAWQ-256 > URL: https://issues.apache.org/jira/browse/HAWQ-256 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF, Security >Reporter: Michael Andre Pearce (IG) >Assignee: Lili Ma > Fix For: backlog > > > Integrate security with Apache Ranger for a unified Hadoop security solution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HAWQ-256) Integrate Security with Apache Ranger
[ https://issues.apache.org/jira/browse/HAWQ-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381645#comment-15381645 ] Hubert Zhang commented on HAWQ-256: --- Don, HAWQ already support JDBC and to lookup for database list and schema list in HAWQ, use the following two commands: For schema list: "select nspname from pg_namespace;" For database list: "\l" I have one more question. How do ranger handle the problem of user names maybe the same in different components. For example user "hubert" may both appear in linux system, HIVE and HAWQ, Do we add a prefix like HIVE.hubert, HAWQ.hubert in RangerPolicyDB? Thanks > Integrate Security with Apache Ranger > - > > Key: HAWQ-256 > URL: https://issues.apache.org/jira/browse/HAWQ-256 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF, Security >Reporter: Michael Andre Pearce (IG) >Assignee: Lili Ma > Fix For: backlog > > > Integrate security with Apache Ranger for a unified Hadoop security solution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #:
Github user xunzhang commented on the pull request: https://github.com/apache/incubator-hawq/commit/15323a501392fc82717dc0b1399497670198e231#commitcomment-18276141 https://github.com/apache/incubator-hawq/pull/797 --- 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-622) fix libhdfs3 readme
[ https://issues.apache.org/jira/browse/HAWQ-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381625#comment-15381625 ] ASF GitHub Bot commented on HAWQ-622: - Github user xunzhang commented on the issue: https://github.com/apache/incubator-hawq/pull/797 Merged into master. > fix libhdfs3 readme > --- > > Key: HAWQ-622 > URL: https://issues.apache.org/jira/browse/HAWQ-622 > Project: Apache HAWQ > Issue Type: Bug > Components: libhdfs >Reporter: Lei Chang >Assignee: hongwu >Priority: Blocker > Fix For: 2.0.0.0-incubating > > > == > Libhdfs3 is developed by Pivotal and used in HAWQ, which > is a massive parallel database engine in Pivotal Hadoop > Distribution. > == > https://github.com/apache/incubator-hawq/blob/bc0904ab02bb3e8c3e3596ce139b3ea6b52e2685/depends/libhdfs3/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq pull request #797: HAWQ-622. Update libhdfs3 readme, clean ol...
Github user xunzhang closed the pull request at: https://github.com/apache/incubator-hawq/pull/797 --- 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-622) fix libhdfs3 readme
[ https://issues.apache.org/jira/browse/HAWQ-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381626#comment-15381626 ] ASF GitHub Bot commented on HAWQ-622: - Github user xunzhang closed the pull request at: https://github.com/apache/incubator-hawq/pull/797 > fix libhdfs3 readme > --- > > Key: HAWQ-622 > URL: https://issues.apache.org/jira/browse/HAWQ-622 > Project: Apache HAWQ > Issue Type: Bug > Components: libhdfs >Reporter: Lei Chang >Assignee: hongwu >Priority: Blocker > Fix For: 2.0.0.0-incubating > > > == > Libhdfs3 is developed by Pivotal and used in HAWQ, which > is a massive parallel database engine in Pivotal Hadoop > Distribution. > == > https://github.com/apache/incubator-hawq/blob/bc0904ab02bb3e8c3e3596ce139b3ea6b52e2685/depends/libhdfs3/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #797: HAWQ-622. Update libhdfs3 readme, clean old strin...
Github user xunzhang commented on the issue: https://github.com/apache/incubator-hawq/pull/797 Merged into master. --- 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-928) Improve user experience of command-line help for hawq CLI utilities
[
https://issues.apache.org/jira/browse/HAWQ-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Chang updated HAWQ-928:
---
Assignee: Radar Lei (was: Lei Chang)
> Improve user experience of command-line help for hawq CLI utilities
> ---
>
> Key: HAWQ-928
> URL: https://issues.apache.org/jira/browse/HAWQ-928
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Command Line Tools, Documentation
>Reporter: Severine Tymon
>Assignee: Radar Lei
>Priority: Minor
> Fix For: backlog
>
>
> This is an umbrella jira that could be broken into smaller pieces if any of
> these improvements are deemed worthwhile/useful. While working with the HAWQ
> CLI, I've noticed some issues with the command help documentation:
> 1) The option used to obtain help is not consistent. Some commands (like hawq
> checkperf) only take the "-?" option, while others do not take "-?" but take
> "-h" or "--help". Some do not take "-h" because there is already an "-h"
> option, typically to supply a hostname.
> 2) Large variations in style and depth of command line help-- some commands
> (like hawq check) are long, man page style help, while others only provide
> brief command usage (hawq config).
> 3) Representations of command-line syntax are inconsistent. Some use <>, some
> use all caps to indicate user-provided values.
> 4) Indicating the default value would be helpful in some cases. For example,
> the --locale, --lc* options of hawq init. (We do provide detailed explanation
> in product docs, but would help if cli informed users where the defaults come
> from if these options are not specified.)
> 5) Outdated external references ("Report bugs to postgresql.org>", EMC download links, Greenplum and gpssh, gpssh)
> 6) Very minor-- Inconsistent word choice, punctuation and spelling
> (capitalization).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HAWQ-622) fix libhdfs3 readme
[ https://issues.apache.org/jira/browse/HAWQ-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381589#comment-15381589 ] ASF GitHub Bot commented on HAWQ-622: - Github user changleicn commented on the issue: https://github.com/apache/incubator-hawq/pull/797 LGTM > fix libhdfs3 readme > --- > > Key: HAWQ-622 > URL: https://issues.apache.org/jira/browse/HAWQ-622 > Project: Apache HAWQ > Issue Type: Bug > Components: libhdfs >Reporter: Lei Chang >Assignee: hongwu >Priority: Blocker > Fix For: 2.0.0.0-incubating > > > == > Libhdfs3 is developed by Pivotal and used in HAWQ, which > is a massive parallel database engine in Pivotal Hadoop > Distribution. > == > https://github.com/apache/incubator-hawq/blob/bc0904ab02bb3e8c3e3596ce139b3ea6b52e2685/depends/libhdfs3/README.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-hawq issue #797: HAWQ-622. Update libhdfs3 readme, clean old strin...
Github user changleicn commented on the issue: https://github.com/apache/incubator-hawq/pull/797 LGTM --- 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-256) Integrate Security with Apache Ranger
[ https://issues.apache.org/jira/browse/HAWQ-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381250#comment-15381250 ] Don Bosco Durai commented on HAWQ-256: -- You got these two correct. We need to add one more to the list. In RangerAdmin UI, when you create a policy, we do auto-suggest by doing a lookup in the databases and schemas in the component. So on the Ranger Admin side, we will need to write the code to query HAWQ. This is generally the existing APIs provided by the components, so in the case HAWQ it would be JDBC or other any other API supported by HAWQ. We just need to track this for completeness purpose and I don't anticipate any work from the HAWQ side. > Integrate Security with Apache Ranger > - > > Key: HAWQ-256 > URL: https://issues.apache.org/jira/browse/HAWQ-256 > Project: Apache HAWQ > Issue Type: New Feature > Components: PXF, Security >Reporter: Michael Andre Pearce (IG) >Assignee: Lili Ma > Fix For: backlog > > > Integrate security with Apache Ranger for a unified Hadoop security solution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
