Re: Review Request 47060: AMBARI-16285 Ranger Tagsync stack changes to sync tags from Atlas

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/47060/#review133167 --- Ship it! Ship It! - Jayush Luniya On May 13, 2016, 10:50

Re: Review Request 47060: AMBARI-16285 Ranger Tagsync stack changes to sync tags from Atlas

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/47060/#review132998 --- @Mugdha, In your patch for AMBARI-13349 you had add logic in

Re: Review Request 47060: AMBARI-16285 Ranger Tagsync stack changes to sync tags from Atlas

> On May 6, 2016, 10:29 a.m., Jonathan Hurley wrote: > > ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py, > > line 230 > > > > > > Not using default? It's 100% guaranteed to

Re: Review Request 47060: AMBARI-16285 Ranger Tagsync stack changes to sync tags from Atlas

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/47060/ --- (Updated May 9, 2016, 5:58 a.m.) Review request for Ambari, Alejandro

Re: Review Request 47060: AMBARI-16285 Ranger Tagsync stack changes to sync tags from Atlas

> On May 6, 2016, 2:29 p.m., Jonathan Hurley wrote: > > These property renames - I don't see them being handled for upgrades. How > > are existing clusters going to adapt to these changes? These properties are introduced in 2.5 stack only which is not released yet. Upgrading to 2.5 will

Re: Review Request 47060: AMBARI-16285 Ranger Tagsync stack changes to sync tags from Atlas

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/47060/#review132031 --- These property renames - I don't see them being handled for