[jira] [Updated] (RANGER-2148) Update Ranger Hive dependency version to 3.0
[ https://issues.apache.org/jira/browse/RANGER-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated RANGER-2148: Priority: Critical (was: Major) > Update Ranger Hive dependency version to 3.0 > - > > Key: RANGER-2148 > URL: https://issues.apache.org/jira/browse/RANGER-2148 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Critical > Fix For: master > > > Update Ranger Hive dependency version to 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2148) Update Ranger Hive dependency version to 3.0
Ramesh Mani created RANGER-2148: --- Summary: Update Ranger Hive dependency version to 3.0 Key: RANGER-2148 URL: https://issues.apache.org/jira/browse/RANGER-2148 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Ramesh Mani Assignee: Ramesh Mani Fix For: master Update Ranger Hive dependency version to 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2125) Improvement in ranger unit test cases.
[ https://issues.apache.org/jira/browse/RANGER-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehul Parikh resolved RANGER-2125. -- Resolution: Fixed > Improvement in ranger unit test cases. > -- > > Key: RANGER-2125 > URL: https://issues.apache.org/jira/browse/RANGER-2125 > Project: Ranger > Issue Type: Test > Components: Ranger >Reporter: Nikhil Purbhe >Assignee: Nikhil Purbhe >Priority: Major > Fix For: 1.1.0 > > > Improvement in ranger unit test cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-2125) Improvement in ranger unit test cases.
[ https://issues.apache.org/jira/browse/RANGER-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehul Parikh reassigned RANGER-2125: Assignee: Nikhil Purbhe > Improvement in ranger unit test cases. > -- > > Key: RANGER-2125 > URL: https://issues.apache.org/jira/browse/RANGER-2125 > Project: Ranger > Issue Type: Test > Components: Ranger >Reporter: Nikhil Purbhe >Assignee: Nikhil Purbhe >Priority: Major > Fix For: 1.1.0 > > > Improvement in ranger unit test cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2126) Improve ranger coverage of unit tests for REST layer.
[ https://issues.apache.org/jira/browse/RANGER-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehul Parikh resolved RANGER-2126. -- Resolution: Fixed Committed on master, ranger-1 and ranger-1.1 https://github.com/apache/ranger/commit/c129e7fefe929db9d7381567227580c0a4821663 > Improve ranger coverage of unit tests for REST layer. > - > > Key: RANGER-2126 > URL: https://issues.apache.org/jira/browse/RANGER-2126 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Nikhil Purbhe >Assignee: Nikhil Purbhe >Priority: Major > Fix For: 1.1.0 > > Attachments: > 0001-RANGER-2126-Improve-ranger-coverage-of-unit-tests-fo.patch > > > Improve coverage for unit tests for REST layer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 67804: Improve ranger coverage of unit tests for REST layer.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67804/#review205675 --- Ship it! Ship It! - Mehul Parikh On July 3, 2018, 7:35 a.m., Nikhil P wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67804/ > --- > > (Updated July 3, 2018, 7:35 a.m.) > > > Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, > Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja > Polavarapu, and Velmurugan Periasamy. > > > Bugs: ranger-2126 > https://issues.apache.org/jira/browse/ranger-2126 > > > Repository: ranger > > > Description > --- > > Improve ranger coverage of unit tests for REST layer. > > > Diffs > - > > > security-admin/src/test/java/org/apache/ranger/rest/TestServiceTagProcessor.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/67804/diff/1/ > > > Testing > --- > > 1.Tested on local machine > > > Thanks, > > Nikhil P > >
Re: Review Request 67804: Improve ranger coverage of unit tests for REST layer.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67804/#review205663 --- Ship it! Ship It! - Velmurugan Periasamy On July 3, 2018, 7:35 a.m., Nikhil P wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67804/ > --- > > (Updated July 3, 2018, 7:35 a.m.) > > > Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, > Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja > Polavarapu, and Velmurugan Periasamy. > > > Bugs: ranger-2126 > https://issues.apache.org/jira/browse/ranger-2126 > > > Repository: ranger > > > Description > --- > > Improve ranger coverage of unit tests for REST layer. > > > Diffs > - > > > security-admin/src/test/java/org/apache/ranger/rest/TestServiceTagProcessor.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/67804/diff/1/ > > > Testing > --- > > 1.Tested on local machine > > > Thanks, > > Nikhil P > >
[jira] [Updated] (RANGER-1643) Handle multiple comma in credentials ...
[ https://issues.apache.org/jira/browse/RANGER-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-1643: - Fix Version/s: (was: 1.1.0) > Handle multiple comma in credentials ... > > > Key: RANGER-1643 > URL: https://issues.apache.org/jira/browse/RANGER-1643 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.6.3, 0.7.1 >Reporter: Selvamohan Neethiraj >Assignee: Endre Kovacs >Priority: Minor > Attachments: > 0001-RANGER-1644-RANGER-1643-using-stronger-crypto-algo-s.patch > > > Currently, PasswordUtils parses the encryption configuration based on the > presence of a comma character. The actual password itself may have comma > characters. We should fix this to allow the user with the password or we > should remove the code that handles the password without having encryption > configuration as part of the input string. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1645) Update Doc/Wiki to provide details on using custom encryption key and salt for encryption of credentials
[ https://issues.apache.org/jira/browse/RANGER-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-1645: - Fix Version/s: (was: 1.1.0) > Update Doc/Wiki to provide details on using custom encryption key and salt > for encryption of credentials > > > Key: RANGER-1645 > URL: https://issues.apache.org/jira/browse/RANGER-1645 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Endre Kovacs >Priority: Critical > > Please update the Wiki/Doc to show the process to use custom encryption key > and salt. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1644) Change the default Crypt Algo to use stronger cryptographic algo.
[ https://issues.apache.org/jira/browse/RANGER-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-1644: - Fix Version/s: (was: 1.1.0) > Change the default Crypt Algo to use stronger cryptographic algo. > -- > > Key: RANGER-1644 > URL: https://issues.apache.org/jira/browse/RANGER-1644 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Endre Kovacs >Priority: Critical > Attachments: > 0001-RANGER-1644-replacing-MD5-DES-with-SHA512-AES128.patch > > > Change the default crypt algorithm to use a stronger cipher algorithm -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 67804: Improve ranger coverage of unit tests for REST layer.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67804/ --- Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy. Bugs: ranger-2126 https://issues.apache.org/jira/browse/ranger-2126 Repository: ranger Description --- Improve ranger coverage of unit tests for REST layer. Diffs - security-admin/src/test/java/org/apache/ranger/rest/TestServiceTagProcessor.java PRE-CREATION Diff: https://reviews.apache.org/r/67804/diff/1/ Testing --- 1.Tested on local machine Thanks, Nikhil P
Re: Ranger 1.1 release
Thanks Rangers. I have started Ranger 1.1.0 release process with below activities. Please resolve open JIRAs slated for 1.1.0 as soon as possible, tomorrow I will move open items to 2.0.0. Let’s target to release 1.1.0 asap. — Created https://issues.apache.org/jira/browse/RANGER-2147 to track 1.1.0 release activity. — Created a new release branch ranger–1.1 to stabilize the release. Version is set to 1.1.0. Please push any commits intended for 1.1.0 to this branch (in addition to master). — Created a new branch ranger–1 to be used for branching any new 1.X release in future. Version in ranger-1 branch is set to 1.2.0-SNAPSHOT. Please note that any back ports from master to ranger-1.0, ranger-1.1 should be committed also to ranger-1 to keep future 1.X branching intact. This is modeled on hadoop release versioning mentioned at https://hadoop.apache.org/versioning.html — Created a new release version 2.0.0 in Apache Ranger JIRA. — Set master branch version to 2.0.0-SNAPSHOT Thanks again, Vel --- From: Madhan Neethiraj Reply-To: "dev@ranger.apache.org" Date: Thursday, June 28, 2018 at 11:32 AM To: "dev@ranger.apache.org" Subject: Re: Ranger 1.1 release +1 for the release. On 6/26/18, 10:45 PM, "Mehul Parikh" wrote: +1 On Wed, Jun 27, 2018 at 9:46 AM, PradeeP AgrawaL < pradeepagrawal8...@gmail.com> wrote: > +1 > > > Regards, > PradeeP > > On 25 June 2018 at 15:04, Colm O hEigeartaigh wrote: > > > +1. > > > > Colm. > > > > On Sun, Jun 24, 2018 at 9:18 PM, Zsombor Gegesy > > wrote: > > > > > +1 - I believe in the "release early release often" mantra :) > > > > > > > > > Regards, > > > Zsombor > > > > > > On Sun, Jun 24, 2018 at 5:56 PM, Srikanth Venkat < > > sven...@hortonworks.com> > > > wrote: > > > > > > > +1, it would be nice to have a Ranger release baseline that aligns > with > > > > Atlas 1.0. > > > > Thanks Vel for taking the initiative! > > > > > > > > Thx > > > > Srikanth Venkat > > > > sven...@hortonworks.com > > > > > > > > On 6/22/18, 10:24 PM, "Balaji Ganesan" > > > > wrote: > > > > > > > > +1. Vel, thanks for taking the initiative. > > > > > > > > On Fri, Jun 22, 2018 at 7:51 PM Jianhua Peng < > > pengjian...@apache.org > > > > > > > > wrote: > > > > > > > > > +1 > > > > > > > > > > Thank you, > > > > > Jianhua Peng. > > > > > > > > > > On 2018/06/22 16:25:45, Velmurugan Periasamy > > > wrote: > > > > > > Rangers: > > > > > > > > > > > > Now that support for Atlas 1.0 is added ( > > > > > https://issues.apache.org/jira/browse/RANGER-2136 < > > > > > https://issues.apache.org/jira/browse/RANGER-2136>), I propose > > to > > > > release > > > > > Ranger 1.1 (tentative first week of July). > > > > > > > > > > > > I request the community to resolve open JIRA’s marked for 1.1 > > in > > > > the > > > > > next couple of weeks or move them to next release. My proposal > is > > > to > > > > call > > > > > next release 2.0 and update master to 2.0.0-SNAPSHOT. > > > > > > > > > > > > Thank you, > > > > > > Vel > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Colm O hEigeartaigh > > > > Talend Community Coder > > http://coders.talend.com > > > -- Thanks and regards, Mehul Parikh M: +91 98191 54446 E: xsme...@gmail.com
