[Subtask] Remove MANAGED_BY_GRAVITINO limit #5336
Assignees
Labels
subtask
Subtasks of umbrella issue
Comments
17 tasks
xunliu
added a commit
to xunliu/gravitino
that referenced
this issue
Oct 29, 2024
xunliu
changed the title
theoryxu
pushed a commit
to theoryxu/gravitino
that referenced
this issue
Nov 20, 2024
… compatible for existing ranger policy
theoryxu
pushed a commit
to theoryxu/gravitino
that referenced
this issue
Nov 20, 2024
… compatible for existing ranger policy
theoryxu
pushed a commit
to theoryxu/gravitino
that referenced
this issue
Nov 20, 2024
… compatible for existing ranger policy
theoryxu
pushed a commit
to theoryxu/gravitino
that referenced
this issue
Nov 21, 2024
… compatible for existing ranger policy
theoryxu
pushed a commit
to theoryxu/gravitino
that referenced
this issue
Nov 21, 2024
theoryxu
pushed a commit
to theoryxu/gravitino
that referenced
this issue
Nov 21, 2024
… compatible for existing ranger policy
theoryxu
pushed a commit
to theoryxu/gravitino
that referenced
this issue
Nov 21, 2024
… compatible for existing ranger policy
theoryxu
pushed a commit
to theoryxu/gravitino
that referenced
this issue
Nov 22, 2024
… compatible for existing ranger policy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the subtask
Currently, Gravitino only operation have
MANAGED_BY_GRAVITINOlabel's Ranger Policy.If a user has a Ranger service and this Ranger already has some Ranger Policy.
When Gravitino will push down a Ranger Policy, if this Policy manage resource already exist in the Ranger service and this Policy doesn't have
MANAGED_BY_GRAVITINOlabel, then Gravitino will throw exception.Parent issue
#5115
The text was updated successfully, but these errors were encountered: