[
https://issues.apache.org/jira/browse/HAWQ-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367129#comment-15367129
]
ASF GitHub Bot commented on HAWQ-872:
-------------------------------------
GitHub user radarwave opened a pull request:
https://github.com/apache/incubator-hawq/pull/780
HAWQ-872 Fix HAWQ check fails when kerberos is enabled
When kerberos is enabled, we run 'hawq check' without '--kerberos' option,
it will give 'global name 'hadoop' is not defined' error.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/radarwave/incubator-hawq checkk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/780.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 #780
----
commit c36b62cf47fcee5d591dc03eb7fc16193d8c88fa
Author: rlei <[email protected]>
Date: 2016-07-06T08:25:30Z
HAWQ-872 Fix HAWQ check fails when kerberos is enabled
When kerberos is enabled, we run 'hawq check' without '--kerberos' option,
it will give 'global name 'hadoop' is not defined' error.
----
> HAWQ check fails if '--kerberos' not given when kerberos is actually enabled
> -----------------------------------------------------------------------------
>
> Key: HAWQ-872
> URL: https://issues.apache.org/jira/browse/HAWQ-872
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Command Line Tools
> Reporter: Radar Lei
> Assignee: Radar Lei
>
> When kerberos is enabled, we run 'hawq check' without '--kerberos' option, it
> will give 'global name 'hadoop' is not defined' error.
> See:
> checkFailed(host.hostname, "HAWQ configuration: expected '%s' for '%s',
> actual value is '%s'" % ('simple', 'hadoop.security.authentication',
> actual_config[hadoop.security.authentication]))
> NameError: global name 'hadoop' is not defined
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
