You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Bartosz Krasiński (Jira)" <ji...@apache.org> on 2020/06/01 07:05:00 UTC

[jira] [Created] (FLINK-18045) Newest version reintroduced a bug causing not working on secured MapR

Bartosz Krasiński created FLINK-18045:
-----------------------------------------

             Summary: Newest version reintroduced a bug causing not working on secured MapR
                 Key: FLINK-18045
                 URL: https://issues.apache.org/jira/browse/FLINK-18045
             Project: Flink
          Issue Type: Bug
          Components: Deployment / YARN
    Affects Versions: 1.10.1
            Reporter: Bartosz Krasiński


I was not able to run Flink 1.10.1 on YARN on a a secured MapR cluster, but the previous version (1.10.0) works fine.

After some investigation it looks like during some refactoring, checking if the enabled security method is kerberos was removed, effectively reintroducing https://issues.apache.org/jira/browse/FLINK-5949

 

Refactoring commit: [https://github.com/apache/flink/commit/8751e69037d8a9b1756b75eed62a368c3ef29137]

 

My proposal would be to bring back the kerberos check:
{code:java}
loginUser.getAuthenticationMethod() == UserGroupInformation.AuthenticationMethod.KERBEROS
{code}
and add an unit test for that case to prevent it from happening again

I'm happy to prepare a PR after reaching consensus



--
This message was sent by Atlassian Jira
(v8.3.4#803005)