Qiang Zhang created RANGER-1887:
---
Summary: serviceDef.getResources().get(0).getName(); case
IndexOutOfBoundsException in RangerServiceTag.class And print error in
RangerServiceStorm
Key: RANGER-1887
URL: https://
[
https://issues.apache.org/jira/browse/RANGER-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Galave reopened RANGER-1860:
--
> Provide a new service interface prompt function framework to resolved the
> defect of the curren
[
https://issues.apache.org/jira/browse/RANGER-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250867#comment-16250867
]
Nitin Galave commented on RANGER-1860:
--
[~zhangqiang2] Can you handle the same scena
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63785/
---
Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay
Ku
[
https://issues.apache.org/jira/browse/RANGER-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bhavik patel updated RANGER-1884:
-
Attachment: RANGER-1884.patch
> Default Policy is not created for Ranger KMS and Tag service
> --
Madhan Neethiraj created RANGER-1886:
Summary: TagSync updates for the changes in Atlas API
Key: RANGER-1886
URL: https://issues.apache.org/jira/browse/RANGER-1886
Project: Ranger
Issue T
[
https://issues.apache.org/jira/browse/RANGER-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249714#comment-16249714
]
Endre Kovacs commented on RANGER-1643:
--
you are right [~bpatel], i'll do proceed wit
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63700/#review190819
---
Ship it!
Ship It!
- Colm O hEigeartaigh
On Nov. 9, 2017, 1:4
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63756/
---
Review request for ranger.
Bugs: RANGER-1738
https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/RANGER-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1738:
Attachment: 0001-RANGER-1738-RangerYarnAuthorizer-not-compatible-with.patch
A patch
Hi Madhan,
Just a follow up on this issue. I was thinking the easiest way to solve it
is to follow your first suggestion to remove the implied grant. However,
the problem is that this implied grant exists in Yarn itself. So if "alice"
is granted the "administer queue" permission only, she can stil
[
https://issues.apache.org/jira/browse/RANGER-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh closed RANGER-1339.
---
> DENY and ALLOW EXCLUSION do not work with YARN
> --
[
https://issues.apache.org/jira/browse/RANGER-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved RANGER-1339.
-
Resolution: Won't Fix
See https://issues.apache.org/jira/browse/RANGER-1885 inst
Colm O hEigeartaigh created RANGER-1885:
---
Summary: Remove implied grant for the administer queue permission
for the Yarn plugin
Key: RANGER-1885
URL: https://issues.apache.org/jira/browse/RANGER-1885
> On Nov. 10, 2017, 7:43 a.m., Madhan Neethiraj wrote:
> > I think the special handling of implied grants of "ALL", in deny and
> > allow-exceptions, would be confusing. Currently Ranger policy model treats
> > all access-types the same - there is no special treatment for "ALL". Also,
> > the
15 matches
Mail list logo
