Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support kerberos authentication for Kudu connector #13968

Closed
wants to merge 3 commits into from
Closed

Support kerberos authentication for Kudu connector #13968

wants to merge 3 commits into from

Conversation

liyubin117
Copy link
Contributor

@liyubin117 liyubin117 commented Jan 15, 2020

Add the following configuration to etc/catalog/kudu.properties to enable kerberos authentication:
kudu.kerberos-auth.enabled=true
kudu.kerberos-auth.debug.enabled=true
kudu.kerberos-auth.principal=xxx
kudu.kerberos-auth.keytab=xxx.keytab

== RELEASE NOTES ==

Kudu Changes

  • support kerberos authentication

@liyubin117 liyubin117 requested review from arhimondr, wenleix and rongrong and removed request for arhimondr January 19, 2020 02:16
Copy link
Contributor

@wenleix wenleix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One question about hadoop-common dependency. Otherwise, looks good.

Can we squash the 3 commits?

@liyubin117
Copy link
Contributor Author

liyubin117 commented Jan 23, 2020

@wenleix @arhimondr
Thank you very much, I have resolved the problems as you said before, I have created another pr, please have a look :)
#14007

@liyubin117 liyubin117 closed this Jan 23, 2020
@wenleix
Copy link
Contributor

wenleix commented Jan 24, 2020

@liyubin117 : Looks like you accidentally remove you repo (and cause the PR to be closed)?

@liyubin117
Copy link
Contributor Author

liyubin117 commented Jan 24, 2020

@liyubin117 : Looks like you accidentally remove you repo (and cause the PR to be closed)?

the commits previously were redundancy, I have squashed them in a new repo and fix the problems as you figured in #14007, but a new repo seem not nessesary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants