[jira] [Comment Edited] (RANGER-3685) hive 'show' sql produces excessive audit log

2022-10-10 Thread Madhan Neethiraj (Jira) 


[ 
https://issues.apache.org/jira/browse/RANGER-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615409#comment-17615409
 ] 

Madhan Neethiraj edited comment on RANGER-3685 at 10/11/22 3:36 AM:


[~Xuze Yang]  - RANGER-3000 introduced audit-filtering feature, which enables 
to skip generation of audit logs for conditions specified in 
service-configuration. Default service-configuration for Hive was updated in 
RANGER-3214 (shown below) to skip auditing of METADATA OPERATIONS, like SHOW 
DATABASES. Note the following text in Hive service-def configuration: 
{code:java}
{'actions':['METADATA OPERATION'], 'isAudited': false}{code}
 
{code:java}
 {
    "itemId":        6,
    "name":         "ranger.plugin.audit.filters",
    "type":         "string",
    "mandatory":    false,
    "label":        "Ranger Default Audit Filters",
    "defaultValue": "[ {'accessResult': 'DENIED', 'isAudited': true}, 
{'actions':['METADATA OPERATION'], 'isAudited': false}, 
{'users':['hive','hue'],'actions':['SHOW_ROLES'],'isAudited':false} ]"
  }{code}
 

Can you please verify the configuration of your Hive service (like dev_hive) if 
appropriate value is specified for "ranger.plugin.audit.filters"?


was (Author: madhan.neethiraj):
[~Xuze Yang]  - RANGER-3000 introduced audit-filtering feature, which enables 
to skip generation of audit logs for conditions specified in 
service-configuration. Default service-configuration for Hive was updated in 
RANGER-3214 (shown below) to skip auditing of METADATA OPERATIONS, like SHOW 
DATABASES. Note the following text in Hive service-def configuration: 
{code:java}
{'actions':['METADATA OPERATION'], 'isAudited': false}{code}
 

 

 
{code:java}
 {
    "itemId":        6,
    "name":         "ranger.plugin.audit.filters",
    "type":         "string",
    "mandatory":    false,
    "label":        "Ranger Default Audit Filters",
    "defaultValue": "[ {'accessResult': 'DENIED', 'isAudited': true}, 
{'actions':['METADATA OPERATION'], 'isAudited': false}, 
{'users':['hive','hue'],'actions':['SHOW_ROLES'],'isAudited':false} ]"
  }{code}
 

Can you please verify the configuration of your Hive service (like dev_hive) if 
appropriate value is specified for "ranger.plugin.audit.filters".

> hive 'show' sql produces excessive audit log
> 
>
> Key: RANGER-3685
> URL: https://issues.apache.org/jira/browse/RANGER-3685
> Project: Ranger
>  Issue Type: Improvement
>  Components: audit
>Affects Versions: 2.1.0
>Reporter: Xuze Yang
>Assignee: Xuze Yang
>Priority: Major
> Attachments: 
> RANGER-3685-hive-show-sql-produces-excessive-audit-l.patch
>
>
> Since ranger2.1.0. For "show databases", user needs any permission on 
> Database to get authorized. RangerHiveAuthorizer.filterListCmdObjects() is 
> implemented to filter out the database which user don't have access to. 
> This is a good implementation, but a problem comes with it：the method will 
> record an audit log for each database(each table for "show tables"). In our 
> production environment, There are 80,000 tables under a database of hive. A 
> show tables operation will generate 80001(The extra one is the verification 
> of USE permissions) audit logs. Unfortunately, our customers will frequently 
> call the show tables operation.
> This brings up two problems: 
>  # Valuable audit logs are flooded
>  # Take up a lot of storage resources
> For problem.2, such a scenario has occurred in our environment: our audit log 
> destination is down. All audit logs are spooled in disk files, several days 
> later, the size of the disk file exceeded 800G, causing other components to 
> fail to provide services normally.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74148: Roles deletion Takes time in Apache Ranger when there are more users, groups, roles

2022-10-10 Thread Ramachandran Krishnan 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74148/
---

(Updated Oct. 11, 2022, 3:33 a.m.)


Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, Nikhil P, Pradeep 
Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan 
Periasamy.


Bugs: RANGER-3900
https://issues.apache.org/jira/browse/RANGER-3900


Repository: ranger


Description
---

We used DB batch write call instead of 1 DB write call for every 
user,role,group deference


Diffs (updated)
-

  security-admin/src/main/java/org/apache/ranger/biz/RoleRefUpdater.java 
56f7ec4c8 
  security-admin/src/main/java/org/apache/ranger/common/db/BaseDao.java 
fc56ff88b 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyRefAccessTypeDao.java 
a8233e30c 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyRefConditionDao.java 
bc17fcdb0 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyRefDataMaskTypeDao.java
 df5f7cd94 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyRefGroupDao.java 
dc41aeadb 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyRefResourceDao.java 
738c6ff49 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyRefRoleDao.java 
35433c758 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyRefUserDao.java 
eced7b261 
  security-admin/src/main/java/org/apache/ranger/db/XXRoleRefGroupDao.java 
eb470f260 
  security-admin/src/main/java/org/apache/ranger/db/XXRoleRefRoleDao.java 
8f6fc8cfa 
  security-admin/src/main/java/org/apache/ranger/db/XXRoleRefUserDao.java 
ba9fb494b 
  security-admin/src/main/resources/META-INF/jpa_named_queries.xml e4a2354b0 


Diff: https://reviews.apache.org/r/74148/diff/5/

Changes: https://reviews.apache.org/r/74148/diff/4-5/


Testing
---

test with 1 Role contains 1k other roles and 1k groups 
while deleting the role it took 11.577 seconds
After fix
it took 1.021 seconds


Thanks,

Ramachandran Krishnan

Re: Review Request 74136: RANGER-3685:hive 'show' sql produces excessive audit log

2022-10-10 Thread Madhan Neethiraj 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74136/#review224773
---




hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java
Lines 1132 (patched)


RANGER-3000 introduced audit-filtering feature, which enables to skip 
generation of audit logs for conditions specified in service-configuration. 
Default service-configuration for Hive was updated in RANGER-3214 (shown below) 
to skip auditing of METADATA OPERATIONS, like SHOW DATABASES. Note the 
following text in Hive service-def configuration: 

{'actions':['METADATA OPERATION'], 'isAudited': false}
 

{
  "itemId":6,
  "name": "ranger.plugin.audit.filters",
  "type": "string",
  "mandatory":false,
  "label":"Ranger Default Audit Filters",
  "defaultValue": "[ {'accessResult': 'DENIED', 'isAudited': true}, 
{'actions':['METADATA OPERATION'], 'isAudited': false}, 
{'users':['hive','hue'],'actions':['SHOW_ROLES'],'isAudited':false} ]"
}
 

Can you please verify the configuration of your Hive service (like 
dev_hive) if appropriate value is specified for "ranger.plugin.audit.filters"?


- Madhan Neethiraj


On Sept. 24, 2022, 2:37 p.m., Xuze Yang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74136/
> ---
> 
> (Updated Sept. 24, 2022, 2:37 p.m.)
> 
> 
> Review request for ranger, Kirby Zhou, Abhay Kulkarni, and Madhan Neethiraj.
> 
> 
> Bugs: RANGER-3685
> https://issues.apache.org/jira/browse/RANGER-3685
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> hive show sql produces too many audit logs, which will flood valuable audit 
> logs and take up a lot of storage resources. This patch aims to provide a 
> configuration item to support simplified hive audit logging
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/authorization/hadoop/constants/RangerHadoopConstants.java
>  6675125e1 
>   
> hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java
>  8f6801be1 
> 
> 
> Diff: https://reviews.apache.org/r/74136/diff/1/
> 
> 
> Testing
> ---
> 
> 1. when configuration "xasecure.hive.simplify.audit.of.hive.show.sql" is not 
> set or set to false. The code behaves the same as before,i.e record audit 
> logs for each databases or tables
> 2. when configuration "xasecure.hive.simplify.audit.of.hive.show.sql" is set 
> to true. It will only record an audit log about USE operation
> 
> 
> Thanks,
> 
> Xuze Yang
> 
>

[jira] [Commented] (RANGER-3685) hive 'show' sql produces excessive audit log

2022-10-10 Thread Madhan Neethiraj (Jira) 


[ 
https://issues.apache.org/jira/browse/RANGER-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615409#comment-17615409
 ] 

Madhan Neethiraj commented on RANGER-3685:
--

[~Xuze Yang]  - RANGER-3000 introduced audit-filtering feature, which enables 
to skip generation of audit logs for conditions specified in 
service-configuration. Default service-configuration for Hive was updated in 
RANGER-3214 (shown below) to skip auditing of METADATA OPERATIONS, like SHOW 
DATABASES. Note the following text in Hive service-def configuration: 
{code:java}
{'actions':['METADATA OPERATION'], 'isAudited': false}{code}
 

 

 
{code:java}
 {
    "itemId":        6,
    "name":         "ranger.plugin.audit.filters",
    "type":         "string",
    "mandatory":    false,
    "label":        "Ranger Default Audit Filters",
    "defaultValue": "[ {'accessResult': 'DENIED', 'isAudited': true}, 
{'actions':['METADATA OPERATION'], 'isAudited': false}, 
{'users':['hive','hue'],'actions':['SHOW_ROLES'],'isAudited':false} ]"
  }{code}
 

Can you please verify the configuration of your Hive service (like dev_hive) if 
appropriate value is specified for "ranger.plugin.audit.filters".

> hive 'show' sql produces excessive audit log
> 
>
> Key: RANGER-3685
> URL: https://issues.apache.org/jira/browse/RANGER-3685
> Project: Ranger
>  Issue Type: Improvement
>  Components: audit
>Affects Versions: 2.1.0
>Reporter: Xuze Yang
>Assignee: Xuze Yang
>Priority: Major
> Attachments: 
> RANGER-3685-hive-show-sql-produces-excessive-audit-l.patch
>
>
> Since ranger2.1.0. For "show databases", user needs any permission on 
> Database to get authorized. RangerHiveAuthorizer.filterListCmdObjects() is 
> implemented to filter out the database which user don't have access to. 
> This is a good implementation, but a problem comes with it：the method will 
> record an audit log for each database(each table for "show tables"). In our 
> production environment, There are 80,000 tables under a database of hive. A 
> show tables operation will generate 80001(The extra one is the verification 
> of USE permissions) audit logs. Unfortunately, our customers will frequently 
> call the show tables operation.
> This brings up two problems: 
>  # Valuable audit logs are flooded
>  # Take up a lot of storage resources
> For problem.2, such a scenario has occurred in our environment: our audit log 
> destination is down. All audit logs are spooled in disk files, several days 
> later, the size of the disk file exceeded 800G, causing other components to 
> fail to provide services normally.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74134: RANGER-3888, RANGER-3887, RANGER-3886, RANGER-3931: Validity Scheduler , recurrence schedule: added validation

2022-10-10 Thread Mehul Parikh 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74134/#review224772
---


Ship it!




Ship It!

- Mehul Parikh


On Sept. 28, 2022, 8:20 a.m., Dineshkumar Yadav wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74134/
> ---
> 
> (Updated Sept. 28, 2022, 8:20 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Jayendra Parab, Kishor Gollapalliwar, 
> Abhay Kulkarni, Pradeep Agrawal, Ramesh Mani, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3886, RANGER-3887, RANGER-3888, and RANGER-3931
> https://issues.apache.org/jira/browse/RANGER-3886
> https://issues.apache.org/jira/browse/RANGER-3887
> https://issues.apache.org/jira/browse/RANGER-3888
> https://issues.apache.org/jira/browse/RANGER-3931
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> below validation is added for Validity Scheduler and recurrence schedule.
> 1. When there is no interval but schedule is specified , policy is created
> 2. Ranger accepts invalid start/endTime
> 3. Ranger reports overlapping ranges though there are no overlapping values
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerValidityScheduleValidator.java
>  2b4b049fa 
> 
> 
> Diff: https://reviews.apache.org/r/74134/diff/2/
> 
> 
> Testing
> ---
> 
> tested using curl request.
> 
> 
> Thanks,
> 
> Dineshkumar Yadav
> 
>

[jira] [Commented] (RANGER-3929) To support batching in SQL IN clause of SQL queries used in Ranger

2022-10-10 Thread Ramachandran (Jira) 


[ 
https://issues.apache.org/jira/browse/RANGER-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615010#comment-17615010
 ] 

Ramachandran commented on RANGER-3929:
--

Sure I closed [https://reviews.apache.org/r/74138/]

> To support batching in SQL IN clause of SQL queries used in Ranger
> --
>
> Key: RANGER-3929
> URL: https://issues.apache.org/jira/browse/RANGER-3929
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 3.0.0
>Reporter: Ramachandran
>Assignee: Ramachandran
>Priority: Major
> Attachments: 
> 0001-RANGER-3929-To-support-batching-in-SQL-IN-clause-of-.patch
>
>
> As of  now, we are not handling the max values that will be passed into the 
> IN clause SQL queries
> Most of the databases which support maximum of 1000 values in the IN clause 
>  
>  
> {code:java}
> getEntityManager()
> .createNamedQuery("XXPolicyRefUser.deleteByIds", tClass)
> .setParameter("ids", ids).executeUpdate();
>  
> {code}
> We will get the issue when the size grows more than 1000 otherwise we will 
> not face any issue.
> We  need to fix this to avoid the potential bug in the later point of time
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-3929) To support batching in SQL IN clause of SQL queries used in Ranger

2022-10-10 Thread Bhavik Patel (Jira) 


[ 
https://issues.apache.org/jira/browse/RANGER-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615009#comment-17615009
 ] 

Bhavik Patel commented on RANGER-3929:
--

Please close the all the review request.

> To support batching in SQL IN clause of SQL queries used in Ranger
> --
>
> Key: RANGER-3929
> URL: https://issues.apache.org/jira/browse/RANGER-3929
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 3.0.0
>Reporter: Ramachandran
>Assignee: Ramachandran
>Priority: Major
> Attachments: 
> 0001-RANGER-3929-To-support-batching-in-SQL-IN-clause-of-.patch
>
>
> As of  now, we are not handling the max values that will be passed into the 
> IN clause SQL queries
> Most of the databases which support maximum of 1000 values in the IN clause 
>  
>  
> {code:java}
> getEntityManager()
> .createNamedQuery("XXPolicyRefUser.deleteByIds", tClass)
> .setParameter("ids", ids).executeUpdate();
>  
> {code}
> We will get the issue when the size grows more than 1000 otherwise we will 
> not face any issue.
> We  need to fix this to avoid the potential bug in the later point of time
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] (RANGER-3929) To support batching in SQL IN clause of SQL queries used in Ranger

2022-10-10 Thread Bhavik Patel (Jira) 


[ https://issues.apache.org/jira/browse/RANGER-3929 ]


Bhavik Patel deleted comment on RANGER-3929:
--

was (Author: bpatel):
Please close the review request 

> To support batching in SQL IN clause of SQL queries used in Ranger
> --
>
> Key: RANGER-3929
> URL: https://issues.apache.org/jira/browse/RANGER-3929
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 3.0.0
>Reporter: Ramachandran
>Assignee: Ramachandran
>Priority: Major
> Attachments: 
> 0001-RANGER-3929-To-support-batching-in-SQL-IN-clause-of-.patch
>
>
> As of  now, we are not handling the max values that will be passed into the 
> IN clause SQL queries
> Most of the databases which support maximum of 1000 values in the IN clause 
>  
>  
> {code:java}
> getEntityManager()
> .createNamedQuery("XXPolicyRefUser.deleteByIds", tClass)
> .setParameter("ids", ids).executeUpdate();
>  
> {code}
> We will get the issue when the size grows more than 1000 otherwise we will 
> not face any issue.
> We  need to fix this to avoid the potential bug in the later point of time
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74127: Ranger-3880 : Ranger setup fails for newer MySQL versions

2022-10-10 Thread Vishal Suvagia via Review Board 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74127/#review224771
---




kms/scripts/dba_script.py
Lines 167 (patched)


Justus, Thank-you for the fix, the issue is reported for 2.3 version, but 
the fix is already in place for 2.3 version.

kms : 
https://github.com/apache/ranger/blob/ranger-2.3/kms/scripts/db_setup.py#L132-L134

can you kindly share which branch is the fix being applied to, do update 
the review request to reflect the same ?



security-admin/scripts/dba_script.py
Lines 194 (patched)


Same for this fix, it is already available in the 2.3 version:
security-admin : 
https://github.com/apache/ranger/blob/ranger-2.3/security-admin/scripts/db_setup.py#L850-L852


- Vishal Suvagia


On Oct. 6, 2022, 8:24 a.m., Justus wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74127/
> ---
> 
> (Updated Oct. 6, 2022, 8:24 a.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Selvamohan Neethiraj.
> 
> 
> Bugs: RANGER-3880
> https://issues.apache.org/jira/browse/RANGER-3880
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger Setup fails when using newer MySQL which requires to set useSSL to 
> false explicitly
> 
> 
> Diffs
> -
> 
>   kms/scripts/dba_script.py 544c1201b 
>   security-admin/scripts/dba_script.py 0ba396944 
> 
> 
> Diff: https://reviews.apache.org/r/74127/diff/1/
> 
> 
> Testing
> ---
> 
> The setup works fine.
> 
> 
> Thanks,
> 
> Justus
> 
>

[jira] [Commented] (RANGER-3929) To support batching in SQL IN clause of SQL queries used in Ranger

2022-10-10 Thread Bhavik Patel (Jira) 


[ 
https://issues.apache.org/jira/browse/RANGER-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615008#comment-17615008
 ] 

Bhavik Patel commented on RANGER-3929:
--

Please close the review request 

> To support batching in SQL IN clause of SQL queries used in Ranger
> --
>
> Key: RANGER-3929
> URL: https://issues.apache.org/jira/browse/RANGER-3929
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 3.0.0
>Reporter: Ramachandran
>Assignee: Ramachandran
>Priority: Major
> Attachments: 
> 0001-RANGER-3929-To-support-batching-in-SQL-IN-clause-of-.patch
>
>
> As of  now, we are not handling the max values that will be passed into the 
> IN clause SQL queries
> Most of the databases which support maximum of 1000 values in the IN clause 
>  
>  
> {code:java}
> getEntityManager()
> .createNamedQuery("XXPolicyRefUser.deleteByIds", tClass)
> .setParameter("ids", ids).executeUpdate();
>  
> {code}
> We will get the issue when the size grows more than 1000 otherwise we will 
> not face any issue.
> We  need to fix this to avoid the potential bug in the later point of time
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74147: Ranger KMS generates master key on every restart before inserting into DB

2022-10-10 Thread bhavik patel 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74147/#review224770
---



Please update the indentation.

- bhavik patel


On Sept. 29, 2022, 6:44 a.m., Vikas Kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74147/
> ---
> 
> (Updated Sept. 29, 2022, 6:44 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah and Sailaja Polavarapu.
> 
> 
> Bugs: RANGER-3927
> https://issues.apache.org/jira/browse/RANGER-3927
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Issue: Master Key(MK) was being first generated and then it was checking into 
> DB that if MK actually exists on each restart of the KMS process. If exists, 
> it simply returns. The same check could have been added before regenerating 
> the MK to avoid this unnecessary execution.
> 
> FIX: Added the same check before calling the method 
> RangerMasterKey.saveEncryptedMK(). Also removed the check from 
> saveEncryptedMK().
> 
> New logs: If MK doesn't exist, then 
> 
> logger.info("Master Key doesn't exist in DB, Generating the Master Key");
> 
> if MK already exists, then
> 
> logger.debug("Ranger Master Key already exists in the DB, returning.");
> 
> 
> Diffs
> -
> 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerMasterKey.java 
> c37e98ee5 
> 
> 
> Diff: https://reviews.apache.org/r/74147/diff/2/
> 
> 
> Testing
> ---
> 
> verified through logs on restart of the KMS service. And I got "Ranger Master 
> Key already exists in the DB, returning." It was not going to generate and 
> save the MK into DB.
> 
> 
> Thanks,
> 
> Vikas Kumar
> 
>

[jira] [Commented] (RANGER-2128) Implement SparkSQL plugin

2022-10-10 Thread Bhavik Patel (Jira) 


[ 
https://issues.apache.org/jira/browse/RANGER-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614985#comment-17614985
 ] 

Bhavik Patel commented on RANGER-2128:
--

[~jles]  [~kirbyzhou] seems like provided patch is based on reusing of HADOOP 
SQL(Hive) plugin.

> 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
>Assignee: Kent Yao
>Priority: Major
> Attachments: image-2022-10-10-14-25-30-218.png, support_ranger11.tgz
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Implement SparkSQL plugin



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-2128) Implement SparkSQL plugin

2022-10-10 Thread Bhavik Patel (Jira) 


[ 
https://issues.apache.org/jira/browse/RANGER-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614979#comment-17614979
 ] 

Bhavik Patel commented on RANGER-2128:
--

For spark plugin we can use service definition ID as *"204" or* we can use 
*"11"?*

Below ID's are used in the service definition for the different plugins.
!image-2022-10-10-14-25-30-218.png!

> 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
>Assignee: Kent Yao
>Priority: Major
> Attachments: image-2022-10-10-14-25-30-218.png, support_ranger11.tgz
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Implement SparkSQL plugin



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-2128) Implement SparkSQL plugin

2022-10-10 Thread Bhavik Patel (Jira) 


 [ 
https://issues.apache.org/jira/browse/RANGER-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bhavik Patel updated RANGER-2128:
-
Attachment: image-2022-10-10-14-25-30-218.png

> 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
>Assignee: Kent Yao
>Priority: Major
> Attachments: image-2022-10-10-14-25-30-218.png, support_ranger11.tgz
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Implement SparkSQL plugin



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Reopened] (RANGER-3627) Implement Spark extension

2022-10-10 Thread Bhavik Patel (Jira) 


 [ 
https://issues.apache.org/jira/browse/RANGER-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bhavik Patel reopened RANGER-3627:
--

> Implement Spark extension
> -
>
> Key: RANGER-3627
> URL: https://issues.apache.org/jira/browse/RANGER-3627
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Jakub Leś
>Priority: Major
>
> Hi 
> I would like to implement Ranger Spark SQL. Is this ok ?
>  
> Best regards,
> Jakub
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (RANGER-3627) Implement Spark extension

2022-10-10 Thread Bhavik Patel (Jira) 


 [ 
https://issues.apache.org/jira/browse/RANGER-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bhavik Patel resolved RANGER-3627.
--
Resolution: Duplicate

> Implement Spark extension
> -
>
> Key: RANGER-3627
> URL: https://issues.apache.org/jira/browse/RANGER-3627
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Jakub Leś
>Priority: Major
>
> Hi 
> I would like to implement Ranger Spark SQL. Is this ok ?
>  
> Best regards,
> Jakub
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (RANGER-3627) Implement Spark extension

2022-10-10 Thread Bhavik Patel (Jira) 


 [ 
https://issues.apache.org/jira/browse/RANGER-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bhavik Patel resolved RANGER-3627.
--
Resolution: Duplicate

Duplicate of https://issues.apache.org/jira/browse/RANGER-2128

> Implement Spark extension
> -
>
> Key: RANGER-3627
> URL: https://issues.apache.org/jira/browse/RANGER-3627
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Jakub Leś
>Priority: Major
>
> Hi 
> I would like to implement Ranger Spark SQL. Is this ok ?
>  
> Best regards,
> Jakub
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)