FourFriends opened a new issue, #6682: URL: https://github.com/apache/gravitino/issues/6682
### Version main branch ### Describe what's wrong When granting a Role permissions corresponding to Metadata (e.g. ReadFileset, WriteFileset, DropFileset), if there are multiple permissions, their order may be scrambled after being stored in the database (ReadFileset, WriteFileset, DropFileset may be stored randomly in the database). When revoking these permissions, if the permission names do not match, the revoke operation will fail, and the SQL will not be executed. eg. some filesets had binded to a role with same previlege, but the order of previlege are different, <img width="424" alt="Image" src="https://github.com/user-attachments/assets/46757b0e-7586-44f1-9a7b-7b557233b158"; /> which cause revoke permission does not take effect due to the sql  ### Error message and/or stacktrace When we execute the revoke function, it returns success, but in reality, the data is not deleted from the database. ### How to reproduce a file was granted to a role with previlege (ReadFileset, WriteFileset, DropFileset)，then to revoke, the function return success, but in reality, the data is not deleted from the table role_meta_securable_object. ### Additional context _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]
