cuibo01 commented on pull request #16745: URL: https://github.com/apache/flink/pull/16745#issuecomment-899928570
> I prefer to set owner as the current UGI. That means we're following the behavior of hive's default UGI authenticator provider. hi @lirui-apache yes，but in non-secure cluster and authorization is enabled, i am afraid it won't satisfy some existing user scenarios, since the previous owner were empty. we should try to be compatible with previous owner. and in secure cluster and authorization is enabled, if the owner support setting value, this does not comply with the security authentication design. so My previous thought was: if authorization is enabled, and secure cluster, the owner must be current UGI, and owner cannot be set. if authorization is enabled and non-secure cluster, we can set owner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
