[jira] [Updated] (IMPALA-7916) Support for Apache Ranger authorization provider
[ https://issues.apache.org/jira/browse/IMPALA-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7916: -- Fix Version/s: (was: Impala 3.3.0) Impala 3.4.0 > Support for Apache Ranger authorization provider > > > Key: IMPALA-7916 > URL: https://issues.apache.org/jira/browse/IMPALA-7916 > Project: IMPALA > Issue Type: Epic > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Fredy Wijaya >Priority: Critical > Fix For: Impala 3.4.0 > > > Currently Impala has no easy way to support other authorization providers > since the code is very tightly coupled to Sentry. The purpose of this ticket > is to provide support for pluggable authorization provider in Impala. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7916) Support for Apache Ranger authorization provider
[ https://issues.apache.org/jira/browse/IMPALA-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya updated IMPALA-7916: - Priority: Critical (was: Major) > Support for Apache Ranger authorization provider > > > Key: IMPALA-7916 > URL: https://issues.apache.org/jira/browse/IMPALA-7916 > Project: IMPALA > Issue Type: Epic > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Fredy Wijaya >Priority: Critical > Fix For: Impala 3.3.0 > > > Currently Impala has no easy way to support other authorization providers > since the code is very tightly coupled to Sentry. The purpose of this ticket > is to provide support for pluggable authorization provider in Impala. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7916) Support for Apache Ranger authorization provider
[ https://issues.apache.org/jira/browse/IMPALA-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya updated IMPALA-7916: - Epic Name: ranger (was: authz-provider) > Support for Apache Ranger authorization provider > > > Key: IMPALA-7916 > URL: https://issues.apache.org/jira/browse/IMPALA-7916 > Project: IMPALA > Issue Type: Epic > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Fredy Wijaya >Priority: Major > Fix For: Impala 3.3.0 > > > Currently Impala has no easy way to support other authorization providers > since the code is very tightly coupled to Sentry. The purpose of this ticket > is to provide support for pluggable authorization provider in Impala. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7916) Support for Apache Ranger authorization provider
[ https://issues.apache.org/jira/browse/IMPALA-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya updated IMPALA-7916: - Summary: Support for Apache Ranger authorization provider (was: Support for pluggable authorization provider) > Support for Apache Ranger authorization provider > > > Key: IMPALA-7916 > URL: https://issues.apache.org/jira/browse/IMPALA-7916 > Project: IMPALA > Issue Type: Epic > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Fredy Wijaya >Priority: Major > Fix For: Impala 3.3.0 > > > Currently Impala has no easy way to support other authorization providers > since the code is very tightly coupled to Sentry. The purpose of this ticket > is to provide support for pluggable authorization provider in Impala. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
