[GitHub] incubator-hawq issue #1212: HAWQ-1396. Add more test cases for querying exte...
Github user interma commented on the issue: https://github.com/apache/incubator-hawq/pull/1212 Feature-test failed when _TestHawqRanger.PXF*_ tests run parallelly(other ranger tests run serially). Seems they conflict with _TestHawqRanger.Deny*_ tests. So all ranger tests still run serially in this PR, and I will open a new Jira to parallel them in future. --- 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-1424) docs - create ALTER SEQUENCE reference page
[ https://issues.apache.org/jira/browse/HAWQ-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Owen resolved HAWQ-1424. - Resolution: Fixed Fix Version/s: 2.2.0.0-incubating PR merged; resolving and closing. > docs - create ALTER SEQUENCE reference page > --- > > Key: HAWQ-1424 > URL: https://issues.apache.org/jira/browse/HAWQ-1424 > Project: Apache HAWQ > Issue Type: Bug > Components: Documentation >Reporter: Lisa Owen >Assignee: David Yozie > Fix For: 2.2.0.0-incubating > > > docs are missing a reference page for the SQL "ALTER SEQUENCE" command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (HAWQ-1424) docs - create ALTER SEQUENCE reference page
[ https://issues.apache.org/jira/browse/HAWQ-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Owen closed HAWQ-1424. --- > docs - create ALTER SEQUENCE reference page > --- > > Key: HAWQ-1424 > URL: https://issues.apache.org/jira/browse/HAWQ-1424 > Project: Apache HAWQ > Issue Type: Bug > Components: Documentation >Reporter: Lisa Owen >Assignee: David Yozie > Fix For: 2.2.0.0-incubating > > > docs are missing a reference page for the SQL "ALTER SEQUENCE" command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (HAWQ-1427) PXF JSON Profile lang3 dependency error
[ https://issues.apache.org/jira/browse/HAWQ-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivram Mani closed HAWQ-1427. -- > PXF JSON Profile lang3 dependency error > --- > > Key: HAWQ-1427 > URL: https://issues.apache.org/jira/browse/HAWQ-1427 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.3.0.0-incubating > > > Issue with querying JSON data with PXF > Getting the following error > ``` > ERROR: remote component error (500) from '10.101.170.74:51200': type > Exception report message java.lang.Exception: > java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils > description The server encountered an internal error that prevented it from > fulfilling this request.exception javax.servlet.ServletException: > java.lang.Exception: java.lang.NoClassDefFoundError: > org/apache/commons/lang3/StringUtils (libchurl.c:897) (seg9 > AYCAPSU01TS205:4 pid=500623) (dispatcher.c:1801) > ``` > We solved it by manually adding `/usr/local/lib/commons-lang3-3.1.jar` on > Advanced pxf-public-classpath through Ambari. We were also to reproduce it > internally just by following the example from the documentation > (http://hdb.docs.pivotal.io/212/hawq/pxf/JsonPXF.html). > Also noticed the libraries loaded for pxf-service are 2.6 instead: > ```[root@hdp1 ~]# pgrep -fl pxf-service | cut -f1 -d' ' | xargs lsof -p | > grep commons-lang > java372246 pxf memREG8,2 284220 1319168 > /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar > java372246 pxf 62r REG8,2 284220 1319168 > /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar > ``` > So for some reason PXF needs `commons-lang3-3.1.jar`? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (HAWQ-1427) PXF JSON Profile lang3 dependency error
[ https://issues.apache.org/jira/browse/HAWQ-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivram Mani resolved HAWQ-1427. Resolution: Fixed Fix Version/s: 2.3.0.0-incubating Switched to using the available commons.lang instead of lang3 > PXF JSON Profile lang3 dependency error > --- > > Key: HAWQ-1427 > URL: https://issues.apache.org/jira/browse/HAWQ-1427 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > Fix For: 2.3.0.0-incubating > > > Issue with querying JSON data with PXF > Getting the following error > ``` > ERROR: remote component error (500) from '10.101.170.74:51200': type > Exception report message java.lang.Exception: > java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils > description The server encountered an internal error that prevented it from > fulfilling this request.exception javax.servlet.ServletException: > java.lang.Exception: java.lang.NoClassDefFoundError: > org/apache/commons/lang3/StringUtils (libchurl.c:897) (seg9 > AYCAPSU01TS205:4 pid=500623) (dispatcher.c:1801) > ``` > We solved it by manually adding `/usr/local/lib/commons-lang3-3.1.jar` on > Advanced pxf-public-classpath through Ambari. We were also to reproduce it > internally just by following the example from the documentation > (http://hdb.docs.pivotal.io/212/hawq/pxf/JsonPXF.html). > Also noticed the libraries loaded for pxf-service are 2.6 instead: > ```[root@hdp1 ~]# pgrep -fl pxf-service | cut -f1 -d' ' | xargs lsof -p | > grep commons-lang > java372246 pxf memREG8,2 284220 1319168 > /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar > java372246 pxf 62r REG8,2 284220 1319168 > /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar > ``` > So for some reason PXF needs `commons-lang3-3.1.jar`? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-hawq pull request #1214: HAWQ-1427. PXF JSON Profile lang3 to lang...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/1214 --- 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 #1214: HAWQ-1427. PXF JSON Profile lang3 to lang...
GitHub user shivzone opened a pull request: https://github.com/apache/incubator-hawq/pull/1214 HAWQ-1427. PXF JSON Profile lang3 to lang switch You can merge this pull request into a Git repository by running: $ git pull https://github.com/shivzone/incubator-hawq HAWQ-1427 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1214.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 #1214 commit 1a835a94565b9bca540a0a947e6ef52d01de8aab Author: shivzoneDate: 2017-04-07T16:42:18Z HAWQ-1427. PXF JSON Profile lang3 to lang switch --- 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-1427) PXF JSON Profile lang3 dependency error
[ https://issues.apache.org/jira/browse/HAWQ-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961084#comment-15961084 ] Shivram Mani commented on HAWQ-1427: This class is available as part of hive-exec jar which is configured as a run time dependancy in pxf-private.classapth. On clusters which don't have hive rpms this issue would occur. Will switch to using the preexisting org.apache.commons.lang utility instead. > PXF JSON Profile lang3 dependency error > --- > > Key: HAWQ-1427 > URL: https://issues.apache.org/jira/browse/HAWQ-1427 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > > Issue with querying JSON data with PXF > Getting the following error > ``` > ERROR: remote component error (500) from '10.101.170.74:51200': type > Exception report message java.lang.Exception: > java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils > description The server encountered an internal error that prevented it from > fulfilling this request.exception javax.servlet.ServletException: > java.lang.Exception: java.lang.NoClassDefFoundError: > org/apache/commons/lang3/StringUtils (libchurl.c:897) (seg9 > AYCAPSU01TS205:4 pid=500623) (dispatcher.c:1801) > ``` > We solved it by manually adding `/usr/local/lib/commons-lang3-3.1.jar` on > Advanced pxf-public-classpath through Ambari. We were also to reproduce it > internally just by following the example from the documentation > (http://hdb.docs.pivotal.io/212/hawq/pxf/JsonPXF.html). > Also noticed the libraries loaded for pxf-service are 2.6 instead: > ```[root@hdp1 ~]# pgrep -fl pxf-service | cut -f1 -d' ' | xargs lsof -p | > grep commons-lang > java372246 pxf memREG8,2 284220 1319168 > /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar > java372246 pxf 62r REG8,2 284220 1319168 > /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar > ``` > So for some reason PXF needs `commons-lang3-3.1.jar`? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (HAWQ-1427) PXF JSON Profile lang3 dependency error
[ https://issues.apache.org/jira/browse/HAWQ-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivram Mani reassigned HAWQ-1427: -- Assignee: Shivram Mani (was: Ed Espino) > PXF JSON Profile lang3 dependency error > --- > > Key: HAWQ-1427 > URL: https://issues.apache.org/jira/browse/HAWQ-1427 > Project: Apache HAWQ > Issue Type: Bug > Components: PXF >Reporter: Shivram Mani >Assignee: Shivram Mani > > Issue with querying JSON data with PXF > Getting the following error > ``` > ERROR: remote component error (500) from '10.101.170.74:51200': type > Exception report message java.lang.Exception: > java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils > description The server encountered an internal error that prevented it from > fulfilling this request.exception javax.servlet.ServletException: > java.lang.Exception: java.lang.NoClassDefFoundError: > org/apache/commons/lang3/StringUtils (libchurl.c:897) (seg9 > AYCAPSU01TS205:4 pid=500623) (dispatcher.c:1801) > ``` > We solved it by manually adding `/usr/local/lib/commons-lang3-3.1.jar` on > Advanced pxf-public-classpath through Ambari. We were also to reproduce it > internally just by following the example from the documentation > (http://hdb.docs.pivotal.io/212/hawq/pxf/JsonPXF.html). > Also noticed the libraries loaded for pxf-service are 2.6 instead: > ```[root@hdp1 ~]# pgrep -fl pxf-service | cut -f1 -d' ' | xargs lsof -p | > grep commons-lang > java372246 pxf memREG8,2 284220 1319168 > /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar > java372246 pxf 62r REG8,2 284220 1319168 > /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar > ``` > So for some reason PXF needs `commons-lang3-3.1.jar`? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HAWQ-1427) PXF JSON Profile lang3 dependency error
Shivram Mani created HAWQ-1427: -- Summary: PXF JSON Profile lang3 dependency error Key: HAWQ-1427 URL: https://issues.apache.org/jira/browse/HAWQ-1427 Project: Apache HAWQ Issue Type: Bug Components: PXF Reporter: Shivram Mani Assignee: Ed Espino Issue with querying JSON data with PXF Getting the following error ``` ERROR: remote component error (500) from '10.101.170.74:51200': type Exception report message java.lang.Exception: java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils description The server encountered an internal error that prevented it from fulfilling this request.exception javax.servlet.ServletException: java.lang.Exception: java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils (libchurl.c:897) (seg9 AYCAPSU01TS205:4 pid=500623) (dispatcher.c:1801) ``` We solved it by manually adding `/usr/local/lib/commons-lang3-3.1.jar` on Advanced pxf-public-classpath through Ambari. We were also to reproduce it internally just by following the example from the documentation (http://hdb.docs.pivotal.io/212/hawq/pxf/JsonPXF.html). Also noticed the libraries loaded for pxf-service are 2.6 instead: ```[root@hdp1 ~]# pgrep -fl pxf-service | cut -f1 -d' ' | xargs lsof -p | grep commons-lang java372246 pxf memREG8,2 284220 1319168 /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar java372246 pxf 62r REG8,2 284220 1319168 /usr/hdp/2.5.0.0-1245/hadoop/lib/commons-lang-2.6.jar ``` So for some reason PXF needs `commons-lang3-3.1.jar`? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HAWQ-1424) docs - create ALTER SEQUENCE reference page
[ https://issues.apache.org/jira/browse/HAWQ-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961075#comment-15961075 ] ASF GitHub Bot commented on HAWQ-1424: -- Github user lisakowen closed the pull request at: https://github.com/apache/incubator-hawq-docs/pull/117 > docs - create ALTER SEQUENCE reference page > --- > > Key: HAWQ-1424 > URL: https://issues.apache.org/jira/browse/HAWQ-1424 > Project: Apache HAWQ > Issue Type: Bug > Components: Documentation >Reporter: Lisa Owen >Assignee: David Yozie > > docs are missing a reference page for the SQL "ALTER SEQUENCE" command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (HAWQ-1426) hawq extract meets error after the table was reorganized.
[ https://issues.apache.org/jira/browse/HAWQ-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chunling Wang reassigned HAWQ-1426: --- Assignee: Chunling Wang (was: Ed Espino) > hawq extract meets error after the table was reorganized. > - > > Key: HAWQ-1426 > URL: https://issues.apache.org/jira/browse/HAWQ-1426 > Project: Apache HAWQ > Issue Type: Bug > Components: Command Line Tools >Reporter: Lili Ma >Assignee: Chunling Wang > Fix For: 2.3.0.0-incubating > > > After one table is reorganized, hawq extract the table will meet error. > Reproduce Steps: > 1. create an AO table > 2. insert into several records into it > 3. Get the table reorganized. "alter table a set with (reorganize=true);" > 4. run hawq extract, error thrown out. > For the bug fix, we should also guarantee that hawq extract should work if > the table is truncated and re-inserted. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-hawq issue #1213: HAWQ-1426. Fix bug that hawq extract meets error...
Github user zhangh43 commented on the issue: https://github.com/apache/incubator-hawq/pull/1213 +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 #1212: HAWQ-1396. Add more test cases for queryi...
Github user paul-guo- commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1212#discussion_r110351041 --- Diff: src/test/feature/sanity_tests.txt --- @@ -2,5 +2,5 @@ #SERIAL=* are the serial tests to run, optional but should not be empty #you can have several PARALLEL or SRRIAL -PARALLEL=TestErrorTable.*:TestPreparedStatement.*:TestUDF.*:TestAOSnappy.*:TestAlterOwner.*:TestAlterTable.*:TestCreateTable.*:TestGuc.*:TestType.*:TestDatabase.*:TestParquet.*:TestPartition.*:TestSubplan.*:TestAggregate.*:TestCreateTypeComposite.*:TestGpDistRandom.*:TestInformationSchema.*:TestQueryInsert.*:TestQueryNestedCaseNull.*:TestQueryPolymorphism.*:TestQueryPortal.*:TestQueryPrepare.*:TestQuerySequence.*:TestCommonLib.*:TestToast.*:TestTransaction.*:TestCommand.*:TestCopy.*:TestHawqRegister.TestPartitionTableMultilevel:TestHawqRegister.TestUsage1ExpectSuccessDifferentSchema:TestHawqRegister.TestUsage1ExpectSuccess:TestHawqRegister.TestUsage1SingleHawqFile:TestHawqRegister.TestUsage1SingleHiveFile:TestHawqRegister.TestDataTypes:TestHawqRegister.TestUsage1EofSuccess:TestHawqRegister.TestUsage2Case1Expected:TestHawqRegister.TestUsage2Case2Expected -SERIAL=TestHawqRanger.*:TestExternalOid.TestExternalOidAll:TestExternalTable.TestExternalTableAll:TestTemp.BasicTest:TestRowTypes.* +PARALLEL=TestErrorTable.*:TestPreparedStatement.*:TestUDF.*:TestAOSnappy.*:TestAlterOwner.*:TestAlterTable.*:TestCreateTable.*:TestGuc.*:TestType.*:TestDatabase.*:TestParquet.*:TestPartition.*:TestSubplan.*:TestAggregate.*:TestCreateTypeComposite.*:TestGpDistRandom.*:TestInformationSchema.*:TestQueryInsert.*:TestQueryNestedCaseNull.*:TestQueryPolymorphism.*:TestQueryPortal.*:TestQueryPrepare.*:TestQuerySequence.*:TestCommonLib.*:TestToast.*:TestTransaction.*:TestCommand.*:TestCopy.*:TestHawqRegister.TestPartitionTableMultilevel:TestHawqRegister.TestUsage1ExpectSuccessDifferentSchema:TestHawqRegister.TestUsage1ExpectSuccess:TestHawqRegister.TestUsage1SingleHawqFile:TestHawqRegister.TestUsage1SingleHiveFile:TestHawqRegister.TestDataTypes:TestHawqRegister.TestUsage1EofSuccess:TestHawqRegister.TestUsage2Case1Expected:TestHawqRegister.TestUsage2Case2Expected:TestHawqRanger.FallbackTest:TestHawqRanger.PXF* +SERIAL=TestHawqRanger.BasicTest:TestHawqRanger.Allow*:TestHawqRanger.Resource*:TestHawqRanger.Deny*:TestExternalOid.TestExternalOidAll:TestExternalTable.TestExternalTableAll:TestTemp.BasicTest:TestRowTypes.* --- End diff -- I'm wondering whether we could use some more human-readable syntax, e.g. SERIAL=TestHawqRanger.a:TestHawqRanger.b SERIAL+=TestFeatureB.c --- 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-1425) Incorrect init cluster error message while ssh connection failed
[ https://issues.apache.org/jira/browse/HAWQ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radar Lei resolved HAWQ-1425. - Resolution: Fixed > Incorrect init cluster error message while ssh connection failed > > > Key: HAWQ-1425 > URL: https://issues.apache.org/jira/browse/HAWQ-1425 > Project: Apache HAWQ > Issue Type: Bug > Components: Command Line Tools >Affects Versions: 2.1.0.0-incubating >Reporter: Radar Lei >Assignee: Radar Lei > Fix For: 2.2.0.0-incubating > > > If password-less ssh connection is not set, run hawq init cluster will give > wrong error message: > 'This can be run on master host only'. > Actually this might caused by ssh connection to master host failed. We should > handle this situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HAWQ-1425) Incorrect init cluster error message while ssh connection failed
[ https://issues.apache.org/jira/browse/HAWQ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radar Lei updated HAWQ-1425: Affects Version/s: 2.1.0.0-incubating > Incorrect init cluster error message while ssh connection failed > > > Key: HAWQ-1425 > URL: https://issues.apache.org/jira/browse/HAWQ-1425 > Project: Apache HAWQ > Issue Type: Bug > Components: Command Line Tools >Affects Versions: 2.1.0.0-incubating >Reporter: Radar Lei >Assignee: Radar Lei > Fix For: 2.2.0.0-incubating > > > If password-less ssh connection is not set, run hawq init cluster will give > wrong error message: > 'This can be run on master host only'. > Actually this might caused by ssh connection to master host failed. We should > handle this situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HAWQ-1425) Incorrect init cluster error message while ssh connection failed
[ https://issues.apache.org/jira/browse/HAWQ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radar Lei updated HAWQ-1425: Fix Version/s: 2.2.0.0-incubating > Incorrect init cluster error message while ssh connection failed > > > Key: HAWQ-1425 > URL: https://issues.apache.org/jira/browse/HAWQ-1425 > Project: Apache HAWQ > Issue Type: Bug > Components: Command Line Tools >Affects Versions: 2.1.0.0-incubating >Reporter: Radar Lei >Assignee: Radar Lei > Fix For: 2.2.0.0-incubating > > > If password-less ssh connection is not set, run hawq init cluster will give > wrong error message: > 'This can be run on master host only'. > Actually this might caused by ssh connection to master host failed. We should > handle this situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-hawq pull request #1211: HAWQ-1425. Print error message if ssh con...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq/pull/1211 --- 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 #1211: HAWQ-1425. Print error message if ssh con...
Github user radarwave commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1211#discussion_r110341344 --- Diff: tools/bin/hawqpylib/hawqlib.py --- @@ -203,6 +203,13 @@ def check_hostname_equal(remote_host, user = ""): cmd = "hostname" result_local, local_hostname, stderr_remote = local_ssh_output(cmd) result_remote, remote_hostname, stderr_remote = remote_ssh_output(cmd, remote_host, user) +if result_remote != 0: +print "Execute command '%s' failed with return code %d on %s." % (cmd, result_remote, remote_host) +print "Either ssh connection fails or command exits with error. Details:" +print stderr_remote +print "For ssh connection issue, please make sure passwordless ssh is enabled or check remote host." --- End diff -- Although a simple command, it's possible the remote OS have some issue can cause failures. So not only the ssh connection 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. ---
[GitHub] incubator-hawq issue #1213: HAWQ-1426. Fix bug that hawq extract meets error...
Github user wcl14 commented on the issue: https://github.com/apache/incubator-hawq/pull/1213 @ictmalili @zhangh43 @interma please review, thanks. --- 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 #1212: HAWQ-1396. Add more test cases for querying exte...
Github user interma commented on the issue: https://github.com/apache/incubator-hawq/pull/1212 @linwen @zhangh43 @stanlyxiang @wcl14 help to review, thanks. --- 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 #1213: HAWQ-1426. Fix bug that hawq extract meet...
GitHub user wcl14 opened a pull request: https://github.com/apache/incubator-hawq/pull/1213 HAWQ-1426. Fix bug that hawq extract meets error after the table was ⦠â¦reorganized You can merge this pull request into a Git repository by running: $ git pull https://github.com/wcl14/incubator-hawq HAWQ-1426 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1213.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 #1213 commit 73a73f717b82a64371a7dff0d3051c65b4652588 Author: Chunling WangDate: 2017-04-07T08:28:22Z HAWQ-1426. Fix bug that hawq extract meets error after the table was reorganized --- 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 #1212: HAWQ-1396. Add more test cases for queryi...
GitHub user interma opened a pull request: https://github.com/apache/incubator-hawq/pull/1212 HAWQ-1396. Add more test cases for querying external table via PXF wi⦠â¦th Ranger enable. include: * add HDFS/Hive/HBase test cases. * add a policy_helper class for add/delete policy conveniently, don't need write policy json file manually now. * some ranger tests can be run parallelly. You can merge this pull request into a Git repository by running: $ git pull https://github.com/interma/interma-hawq hawq-1396 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-hawq/pull/1212.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 #1212 commit ea52b008847d0bfa9653eb3f5d62c266c738437d Author: intermaDate: 2017-04-05T05:47:40Z HAWQ-1396. Add more test cases for querying external table via PXF with Ranger enable. include: * add HDFS/Hive/HBase test cases. * add a policy_helper class for add/delete policy conveniently, donn't need write policy json file manually now. * some ranger tests can be run parallelly. --- 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 #1211: HAWQ-1425. Print error message if ssh con...
Github user huor commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1211#discussion_r110327071 --- Diff: tools/bin/hawqpylib/hawqlib.py --- @@ -203,6 +203,13 @@ def check_hostname_equal(remote_host, user = ""): cmd = "hostname" result_local, local_hostname, stderr_remote = local_ssh_output(cmd) result_remote, remote_hostname, stderr_remote = remote_ssh_output(cmd, remote_host, user) +if result_remote != 0: +print "Execute command '%s' failed with return code %d on %s." % (cmd, result_remote, remote_host) +print "Either ssh connection fails or command exits with error. Details:" +print stderr_remote +print "For ssh connection issue, please make sure passwordless ssh is enabled or check remote host." --- End diff -- The remote command only check if the host exist. ``` if result_remote != 0: print "Execute command '%s' failed with return code %d on %s." % (cmd, result_remote, remote_host) print "Please check ssh connection and make sure passwordless ssh is enabled." ``` --- 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 #1211: HAWQ-1425. Print error message if ssh con...
Github user huor commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1211#discussion_r110323503 --- Diff: tools/bin/hawqpylib/hawqlib.py --- @@ -203,6 +203,13 @@ def check_hostname_equal(remote_host, user = ""): cmd = "hostname" result_local, local_hostname, stderr_remote = local_ssh_output(cmd) result_remote, remote_hostname, stderr_remote = remote_ssh_output(cmd, remote_host, user) +if result_remote != 0: +print stderr_remote +print "Execute remote command failed on %s." % remote_host +print "Either ssh connection fails or command exits with error." +print "For ssh connection issue, please check connection and make sure passwordless ssh enabled." --- End diff -- ``` if result_remote != 0: print "Failed to execute remote command on %s. Either ssh connection issue or command error. Details:" % remote_host print stderr_remote print "Please check connection and make sure passwordless ssh is enabled, or check remote host" ``` --- 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 #1211: HAWQ-1425. Print error message if ssh con...
Github user radarwave commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1211#discussion_r110324197 --- Diff: tools/bin/hawqpylib/hawqlib.py --- @@ -203,6 +203,13 @@ def check_hostname_equal(remote_host, user = ""): cmd = "hostname" result_local, local_hostname, stderr_remote = local_ssh_output(cmd) result_remote, remote_hostname, stderr_remote = remote_ssh_output(cmd, remote_host, user) +if result_remote != 0: +print stderr_remote +print "Execute remote command failed on %s." % remote_host --- End diff -- For Q1, added command line and error code in the error message. For Q2, there are enough error information inside stderr_remote. User can read and know what's happening. --- 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 #1211: HAWQ-1425. Print error message if ssh con...
Github user radarwave commented on a diff in the pull request: https://github.com/apache/incubator-hawq/pull/1211#discussion_r110322606 --- Diff: tools/bin/hawqpylib/hawqlib.py --- @@ -203,6 +203,17 @@ def check_hostname_equal(remote_host, user = ""): cmd = "hostname" result_local, local_hostname, stderr_remote = local_ssh_output(cmd) result_remote, remote_hostname, stderr_remote = remote_ssh_output(cmd, remote_host, user) +# SSH return 255 error code when having connection issues, otherwise return code is in [0, 255). +if result_remote == 255: +print "Create ssh connection to %s failed." % remote_host +print "Please check the ssh connection and make sure passwordless ssh enabled." +sys.exit(result_remote) +elif result_remote > 0: +print "Execute remote command failed." +sys.exit(result_remote) +else: +pass + --- End diff -- Thanks @paul-guo- , print error message is good idea. Fixed. --- 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. ---