bharos opened a new issue, #9902:
URL: https://github.com/apache/gravitino/issues/9902
### What would you like to be improved?
Currently, If a user is not present in a metalake, Gravitino throws an error
```
2026-02-06 00:51:11 WARN [MetadataFilterHelper-ThreadPool-149]
JcasbinAuthorizer:262 - Can not get user user in metalake metalake
org.apache.gravitino.exceptions.NoSuchUserException: User user does not
exist in the metalake metalake
at
org.apache.gravitino.authorization.UserGroupManager.getUser(UserGroupManager.java:122)
~[gravitino-core-1.1.1-SNAPSHOT.jar:?
at
org.apache.gravitino.authorization.AccessControlManager.lambda$getUser$2(AccessControlManager.java:84)
~[gravitino-core-1.1.1-SNAPSHOT.jar:?]
```
This can be an overhead, to add users when an employee joins a company etc..
? Also while onboarding to Gravitino, we need to create 1000s of users.
Why not auto-add ? It doesn't give them any permissions still, until they
have privileges granted
Not suggesting to change the behavior by default, but is it reasonable to
add a config, like
```
# Configuration proposal
gravitino.authorization.auto-create-user: false # default for backward
compatibility
gravitino.authorization.auto-create-user.metalakes: "*" # or
comma-separated list
# Alternative: per-metalake configuration
gravitino.authorization.metalakes.roku.auto-create-user: true
```
### How should we improve?
_No response_
--
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]
