+1 for Apache Ranger Release 2.7.0 

Selva-

> On Jul 2, 2025, at 7:42 PM, Abhishek Kumar <abhishekkumar100...@gmail.com> 
> wrote:
> 
> Thanks Madhan for the initiative.
> 
> +1 for Apache Ranger release 2.7.0.
> 
> I'd like to volunteer to be the release manager for the release.
> 
> Thanks!
> 
> On Wed, Jul 2, 2025 at 4:02 AM Madhan Neethiraj <mad...@apache.org> wrote:
> 
>> Ranger community,
>> 
>> 
>> 
>> The community has added 40+ commits since the release of Apache Ranger
>> 2.6.0 in February this year. I propose we start preparing for Apache Ranger
>> 2.7.0 to include these updates, by mid of July 2025.
>> 
>> 
>> 
>> Git branch ranger-2.7 will be used for this release. If you would like any
>> improvement or fix to be included in this release, please ensure the
>> fix-version is set to 2.7.0 in JIRA.
>> 
>> 
>> 
>> Here are few key improvements:
>> 
>> 
>> 
>> - fix for error while writing audit logs to HDFS
>> 
>> - add config param for writing audits to HDFS in append mode
>> 
>> - API to delete multiple policies
>> 
>> - fix policy label processing in concurrent sessions
>> 
>> - fix for script engine instantiation failure
>> 
>> - fix failure in deleting records from x_auth_sess table
>> 
>> - fix failure in allowing by tags associated with parent resource
>> 
>> - retry GET request on server error in RangerRESTClient
>> 
>> - fix potential NPE in references to RangerBasePlugin.policyEngine
>> 
>> - fix error while migrating Masterkey from older format to external key
>> store
>> 
>> - tag deny policy is not getting enforced on scan table command for hbase
>> 
>> - refactor agents-audit module to move audit destination implementations
>> to separate projects
>> 
>> - dedupTags removes the valid tags while deduplicating tags
>> 
>> - updated plugin classloader to use classloader of shim class as parent
>> 
>> - docker setup improvements
>> 
>> 
>> 
>> Apache Ranger PMC would appreciate your contributions and feedback in
>> getting 2.7.0 release out.
>> 
>> 
>> 
>> Thanks,
>> 
>> Madhan
>> 
>> 
>> 
>> 
>> 
>> 

Reply via email to