[jira] [Commented] (KUDU-2096) Document necessary configuration for Kerberos with master CNAMEs

["Attila Bukor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154186#comment-16154186 ] 

Attila Bukor commented on KUDU-2096:
------------------------------------

It seems this is working fine from Impala also if it's using the correct kudu-client JAR:

{code}
> create table test (id bigint, name string, primary key (id)) partition by hash partitions 2 stored as kudu tblproperties ('kudu.master_addresses' = 'kudu-master');
Query: create table test (id bigint, name string, primary key (id)) partition by hash partitions 2 stored as kudu tblproperties ('kudu.master_addresses' = 'kudu-master')
Fetched 0 row(s) in 0.85s
{code}

> Document necessary configuration for Kerberos with master CNAMEs
> ----------------------------------------------------------------
>
>                 Key: KUDU-2096
>                 URL: https://issues.apache.org/jira/browse/KUDU-2096
>             Project: Kudu
>          Issue Type: Task
>          Components: documentation, security
>            Reporter: Todd Lipcon
>
> Currently our docs recommend using CNAMEs for master addresses to simplify moving them around. However, if clients connect to a master with its non-canonical name, there are some complications with Kerberos principals, etc. We should test and document the necessary steps for such a configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)