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/02/10 18:02:00 UTC
[jira] [Resolved] (IMPALA-9367) Allow specifying MEMORY kerberos
credential cache
[ https://issues.apache.org/jira/browse/IMPALA-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-9367.
-----------------------------------
Resolution: Won't Do
I don't think this is viable at this point because of the need to interoperate with the JVM side of things.
> Allow specifying MEMORY kerberos credential cache
> -------------------------------------------------
>
> Key: IMPALA-9367
> URL: https://issues.apache.org/jira/browse/IMPALA-9367
> Project: IMPALA
> Issue Type: Improvement
> Components: Security
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: kerberos
>
> Currently --krb5_ccname defaults to "/tmp/krb5cc_impala_internal" and requires that the argument be an absolute path.
> Kudu actually defaults to "MEMORY:kudu" as its credential cache, which may have some advantages, e.g. it doesn't depend on the filesystem.
> It would be reasonable to allow setting the credential cache type to MEMORY.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)