[jira] [Commented] (RANGER-2128) Implement SparkSQL plugin
[ https://issues.apache.org/jira/browse/RANGER-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521878#comment-16521878 ] Don Bosco Durai commented on RANGER-2128: - I integrated Ranger with SparkSQL ThriftServer based on [https://github.com/yaooqinn/spark-authorizer.] Since the Thrift Server was based on Hive 1.2, I had to integrate with Ranger 0.5. I have reached out to the developer from the above github to see if he can help us. Spark community has also added hooks to Spark (https://issues.apache.org/jira/browse/SPARK-18127) which can be used to implement Ranger Plugin has first-class integration. > Implement SparkSQL plugin > - > > Key: RANGER-2128 > URL: https://issues.apache.org/jira/browse/RANGER-2128 > Project: Ranger > Issue Type: New Feature > Components: plugins, Ranger >Affects Versions: 1.1.0 >Reporter: t oo >Priority: Major > Fix For: 1.1.0 > > > Implement SparkSQL plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2141) Add PatchForKafkaServiceDefUpdate_J10015.java in consolidated DB schema
[ https://issues.apache.org/jira/browse/RANGER-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521813#comment-16521813 ] bhavik patel commented on RANGER-2141: -- Commit link for master : https://github.com/apache/ranger/commit/da29d1929a54b2b579a74da32e5ea074d0f8e15d > Add PatchForKafkaServiceDefUpdate_J10015.java in consolidated DB schema > --- > > Key: RANGER-2141 > URL: https://issues.apache.org/jira/browse/RANGER-2141 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Mehul Parikh >Assignee: bhavik patel >Priority: Major > Fix For: 1.1.0 > > Attachments: RANGER-2141-master.patch > > > As part of RANGER-2117, PatchForKafkaServiceDefUpdate_J10015.java was added, > need to add that in consolidated db schema. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Fwd: New Defects reported by Coverity Scan for Apache Ranger
Mostly seems to be test code. Still please review…
Thanks
Bosco
> Begin forwarded message:
>
> From: scan-ad...@coverity.com
> Subject: New Defects reported by Coverity Scan for Apache Ranger
> Date: June 24, 2018 at 2:34:29 AM PDT
> To: bo...@apache.org
>
> Hi,
>
> Please find the latest report on new defect(s) introduced to Apache Ranger
> found with Coverity Scan.
>
> 20 new defect(s) introduced to Apache Ranger found with Coverity Scan.
> 6 defect(s), reported by Coverity Scan earlier, were marked fixed in the
> recent build analyzed by Coverity Scan.
>
> New defect(s) Reported-by: Coverity Scan
> Showing 20 of 20 defect(s)
>
>
> ** CID 154572: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
> /tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHbaseResourceMapper.java:
> 144 in
> org.apache.ranger.tagsync.process.TestHbaseResourceMapper.testHbaseResourceFromMissingColumnFamilyName()()
>
>
>
> *** CID 154572: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
> /tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHbaseResourceMapper.java:
> 144 in
> org.apache.ranger.tagsync.process.TestHbaseResourceMapper.testHbaseResourceFromMissingColumnFamilyName()()
> 138 RangerAtlasEntity entity =
> getHbaseColumnFamilyEntity(entAttribs);
> 139
> 140 try {
> 141 RangerServiceResource resource =
> resourceMapper.buildResource(entity);
> 142
> 143 Assert.fail("expected exception. Found " + resource);
CID 154572: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
org.apache.ranger.tagsync.process.TestHbaseResourceMapper.testHbaseResourceFromMissingColumnFamilyName()
might ignore java.lang.Exception.
> 144 } catch(Exception excp) {
> 145 // ignore
> 146 }
> 147 }
> 148
> 149 @Test
>
> ** CID 153272: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
> /tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHdfsResourceMapper.java:
> 155 in
> org.apache.ranger.tagsync.process.TestHdfsResourceMapper.testHdfsResourceFromMissingAttribs()()
>
>
>
> *** CID 153272: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
> /tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHdfsResourceMapper.java:
> 155 in
> org.apache.ranger.tagsync.process.TestHdfsResourceMapper.testHdfsResourceFromMissingAttribs()()
> 149 RangerAtlasEntity entity =
> getHdfsPathEntity(entAttribs);
> 150
> 151 try {
> 152 RangerServiceResource resource =
> resourceMapper.buildResource(entity);
> 153
> 154 Assert.fail("expected exception. Found " +
> resource);
CID 153272: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
org.apache.ranger.tagsync.process.TestHdfsResourceMapper.testHdfsResourceFromMissingAttribs()
might ignore java.lang.Exception.
> 155 } catch(Exception excp) {
> 156 // ignore
> 157 }
> 158 }
> 159
> 160 @Test
>
> ** CID 153259: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
> /tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHiveResourceMapper.java:
> 91 in
> org.apache.ranger.tagsync.process.TestHiveResourceMapper.testHiveResourceFromMissingAttribs()()
>
>
>
> *** CID 153259: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
> /tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHiveResourceMapper.java:
> 91 in
> org.apache.ranger.tagsync.process.TestHiveResourceMapper.testHiveResourceFromMissingAttribs()()
> 85RangerAtlasEntity entity = getHiveDbEntity(entAttribs);
> 86
> 87try {
> 88RangerServiceResource resource =
> resourceMapper.buildResource(entity);
> 89
> 90Assert.fail("expected exception. Found " +
> resource);
CID 153259: FindBugs: Bad practice (FB.DE_MIGHT_IGNORE)
org.apache.ranger.tagsync.process.TestHiveResourceMapper.testHiveResourceFromMissingAttribs()
might ignore java.lang.Exception.
> 91} catch(Exception excp) {
> 92// ignore
> 93}
> 94}
> 95
> 96private RangerAtlasEntity getHiveDbEntity(Map
> entAttribs) throws Exception {
>
> ** CID 150695: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
> /ranger-tools/src/main/java/org/apache/ranger/policyengine/RangerPluginPerfTester.java:
> 145 in
> org.apache.ranger.policyengine.RangerPluginPerfTester.buildConfi
Re: Ranger 1.1 release
+1 - I believe in the "release early release often" mantra :) Regards, Zsombor On Sun, Jun 24, 2018 at 5:56 PM, Srikanth Venkat 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 > 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 > > > > >
Re: Ranger 1.1 release
+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 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 >
