+1 for merging the RANGER-3923 branch into master. Thanks Madhan for the effort. This is a significant enhancement enabling datasets' authorization and auditing.
Regards, Ramesh On Tue, Jan 2, 2024 at 3:01 PM Madhan Neethiraj <[email protected]> wrote: > (apologies for the resend; earlier mail had HTML formatting which got > lost, now sending in plain text format) > > Rangers, > > For more than a year now, Apache Ranger community has been adding > significant enhancements in RANGER-3923 branch. These enhancements enable > business managers to manage access to datasets, instead of having data > owners to manage access to individual resources like tables, columns, > files, directories. > > In addition, this approach offers several benefits including: > - reduced time for users in getting access to data across multiple > services, with a single policy update. > - business managers like project managers to manage access to datasets > instead of multiple data owners, which reduces the time taken to get access > to data. > - separation of responsibilities: data owners focus on building > datasets, while business managers focus on managing access to datasets. > - eliminate the need to update access policies for any changes in > datasets like add/remove/change resources. > > Apache Ranger community has built APIs and UI to manage datasets and > access to datasets. Apache Ranger policy engine has been updated as well to > support datasets. I propose merging these enhancements into master branch > this week, and work towards releasing Apache Ranger 3.0 version, by next > month. Please share your feedback. > > Looking forward to Apache Ranger 3.0 release! > > Thanks, > Madhan > > >
