You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/05/14 17:38:00 UTC
[jira] [Resolved] (IMPALA-3013) Clarify 'Kerberos not installed'
message in impala-shell
[ https://issues.apache.org/jira/browse/IMPALA-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-3013.
-----------------------------------
Resolution: Later
> Clarify 'Kerberos not installed' message in impala-shell
> --------------------------------------------------------
>
> Key: IMPALA-3013
> URL: https://issues.apache.org/jira/browse/IMPALA-3013
> Project: IMPALA
> Issue Type: Improvement
> Components: Security
> Affects Versions: Impala 2.2.4
> Reporter: John Russell
> Priority: Minor
>
> If you run impala-shell -k on a system without the required Kerberos client, you get a message like so:
> {code}
> impala-shell -k -i blah-kerberized.example.com
> Starting Impala Shell using Kerberos authentication
> Using service name 'impala'
> klist not found on the system, install kerberos clients
> {code}
> Because the 'klist not found' message comes after a couple of startup/progress messages from the shell, I thought it connected but then didn't find the right Kerberos infrastructure on the impalad host. It's actually complaining about software missing on the local system where impala-shell is running. Could you add a %s into the 'klist not found' message to echo the hostname, to clarify where exactly the Kerberos client needs to be installed?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)