-
Notifications
You must be signed in to change notification settings - Fork 79
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
Please suggest: Where do we need to create --proxy-user? is it required to be created in Ranger UI only or under hadoop as well? #26
Comments
so i just created an user in hadoop side and one user with same name is created in ranger. But the policies enforced in ranger aren't being applied. |
you can either user proxy user or login user, if you specify --proxy-user UserA , the runtime sparkUser will be UserA, otherwise it will use the user part of spark.yarn.principal configuration. If you are using other authentication method, just pay attention to the value of |
Thanks for reply.
But the setting is not able to enforce ranger policies for this user. Any pointer would be really helpful. |
https://yaooqinn.github.io/spark-authorizer/docs/install_plugin.html please follow this doc to setup |
Thanks for the pointer, BTW we are already using above installation guidelines. Would it cause any problems? |
for spark 2.4 #14 |
Thanks for the pointers, i am looking the ranger-hive-plugin module now. |
Just follow the doc's section 2 |
Still no luck. Also: When i tried installing ranger-hive-plugin on different EMR using below link |
When i try to build locally i get below warning. Also when i tried to run the same code from the spark-shell i get below error. Seems like from spark-shell its not able to access package private class |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: