[jira] [Work started] (IMPALA-8587) Show inherited privileges in show grant w/ Ranger
[ https://issues.apache.org/jira/browse/IMPALA-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8587 started by Austin Nobis. > Show inherited privileges in show grant w/ Ranger > - > > Key: IMPALA-8587 > URL: https://issues.apache.org/jira/browse/IMPALA-8587 > Project: IMPALA > Issue Type: Sub-task > Components: Frontend >Reporter: Austin Nobis >Assignee: Austin Nobis >Priority: Critical > Fix For: Impala 3.3.0 > > > If an admin has privileges from: > *grant all on server to user admin;* > > Currently the command below will show no results: > *show grant user admin on database functional;* > > After the change, the user should see server level privileges from: > *show grant user admin on database functional;* > -- 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-8651) Update grammar for Ranger revoke grant option statement
[ https://issues.apache.org/jira/browse/IMPALA-8651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis updated IMPALA-8651: - Fix Version/s: Impala 3.3.0 Component/s: Frontend > Update grammar for Ranger revoke grant option statement > --- > > Key: IMPALA-8651 > URL: https://issues.apache.org/jira/browse/IMPALA-8651 > Project: IMPALA > Issue Type: Sub-task > Components: Frontend >Reporter: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > *REVOKE GRANT OPTION FOR SELECT ON DATABASE DB FROM USER USR;* > In Ranger, it is not possible to *REVOKE GRANT OPTION* for a specific > privilege (*SELECT*). The *GRANT OPTION* must be revoked for the entire > *DATABASE DB* resource. The Impala grammar should be updated to support > omitting the *FOR SELECT* if the authorization provider is set to Ranger. If > that grammar is used for Sentry, it should throw an exception. -- 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] [Created] (IMPALA-8651) Update grammar for Ranger revoke grant option statement
Austin Nobis created IMPALA-8651: Summary: Update grammar for Ranger revoke grant option statement Key: IMPALA-8651 URL: https://issues.apache.org/jira/browse/IMPALA-8651 Project: IMPALA Issue Type: Sub-task Reporter: Austin Nobis *REVOKE GRANT OPTION FOR SELECT ON DATABASE DB FROM USER USR;* In Ranger, it is not possible to *REVOKE GRANT OPTION* for a specific privilege (*SELECT*). The *GRANT OPTION* must be revoked for the entire *DATABASE DB* resource. The Impala grammar should be updated to support omitting the *FOR SELECT* if the authorization provider is set to Ranger. If that grammar is used for Sentry, it should throw an exception. -- 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] [Work started] (IMPALA-8588) FIx revoke grant option behavior
[ https://issues.apache.org/jira/browse/IMPALA-8588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8588 started by Austin Nobis. > FIx revoke grant option behavior > > > Key: IMPALA-8588 > URL: https://issues.apache.org/jira/browse/IMPALA-8588 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Reporter: Austin Nobis >Assignee: Austin Nobis >Priority: Critical > Fix For: Impala 3.3.0 > > > Given permissions have been granted via: > *grant select on database functional for user admin with grant option;* > > > Currently, running the following statement will remove the *grant option*: > *revoke select on database functional from user admin;* > > The following statement will also not remove the *grant option:* > *revoke grant option for select on database functional from user admin;* > -- 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] [Created] (IMPALA-8588) FIx revoke grant option behavior
Austin Nobis created IMPALA-8588: Summary: FIx revoke grant option behavior Key: IMPALA-8588 URL: https://issues.apache.org/jira/browse/IMPALA-8588 Project: IMPALA Issue Type: Sub-task Components: Frontend Reporter: Austin Nobis Fix For: Impala 3.3.0 Given permissions have been granted via: *grant select on database functional for user admin with grant option;* Currently, running the following statement will remove the *grant option*: *revoke select on database functional from user admin;* The following statement will also not remove the *grant option:* *revoke grant option for select on database functional from user admin;* -- 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-8587) Show inherited privileges in show grant w/ Ranger
[ https://issues.apache.org/jira/browse/IMPALA-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis updated IMPALA-8587: - Summary: Show inherited privileges in show grant w/ Ranger (was: Show inherited privileges in show grant) > Show inherited privileges in show grant w/ Ranger > - > > Key: IMPALA-8587 > URL: https://issues.apache.org/jira/browse/IMPALA-8587 > Project: IMPALA > Issue Type: Improvement > Components: Frontend >Reporter: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > If an admin has privileges from: > *grant all on server to user admin;* > > Currently the command below will show no results: > *show grant user admin on database functional;* > > After the change, the user should see server level privileges from: > *show grant user admin on database functional;* > -- 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] [Created] (IMPALA-8587) Show inherited privileges in show grant
Austin Nobis created IMPALA-8587: Summary: Show inherited privileges in show grant Key: IMPALA-8587 URL: https://issues.apache.org/jira/browse/IMPALA-8587 Project: IMPALA Issue Type: Improvement Components: Frontend Reporter: Austin Nobis Fix For: Impala 3.3.0 If an admin has privileges from: *grant all on server to user admin;* Currently the command below will show no results: *show grant user admin on database functional;* After the change, the user should see server level privileges from: *show grant user admin on database functional;* -- 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] [Assigned] (IMPALA-8248) Improve Ranger test coverage
[ https://issues.apache.org/jira/browse/IMPALA-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis reassigned IMPALA-8248: Assignee: Austin Nobis > Improve Ranger test coverage > > > Key: IMPALA-8248 > URL: https://issues.apache.org/jira/browse/IMPALA-8248 > Project: IMPALA > Issue Type: Sub-task > Components: Infrastructure >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Critical > > We have authorization tests that are specific to Sentry and authorization > tests that can be applicable to any authorization provider. We need to > re-organize the authorization tests to easily differentiate between > Sentry-specific tests vs generic authorization tests. > This also will improve test coverage for Ranger. -- 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] [Created] (IMPALA-8485) References to deprecated feature authorization policy file need to be removed
Austin Nobis created IMPALA-8485: Summary: References to deprecated feature authorization policy file need to be removed Key: IMPALA-8485 URL: https://issues.apache.org/jira/browse/IMPALA-8485 Project: IMPALA Issue Type: Bug Components: Infrastructure Reporter: Austin Nobis Running the command *git grep authz-policy* produces the following output: ** bin/create-test-configuration.sh:generate_config authz-policy.ini.template authz-policy.ini fe/.gitignore:src/test/resources/authz-policy.ini tests/authorization/test_authorization.py:AUTH_POLICY_FILE = "%s/authz-policy.ini" % WAREHOUSE These references to the *authz-policy.ini* should be cleaned up as the authorization policy file feature is deprecated as of *IMPALA-7918.* -- 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] [Assigned] (IMPALA-8292) Misc clean-up after Sentry decoupling
[ https://issues.apache.org/jira/browse/IMPALA-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis reassigned IMPALA-8292: Assignee: Austin Nobis > Misc clean-up after Sentry decoupling > - > > Key: IMPALA-8292 > URL: https://issues.apache.org/jira/browse/IMPALA-8292 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Critical > > The aim of this ticket to do misc code clean up after Sentry decoupling. For > example, renaming names that contain the word Sentry that may no longer be > applicable, updating comments, etc. -- 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] [Work started] (IMPALA-8292) Misc clean-up after Sentry decoupling
[ https://issues.apache.org/jira/browse/IMPALA-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8292 started by Austin Nobis. > Misc clean-up after Sentry decoupling > - > > Key: IMPALA-8292 > URL: https://issues.apache.org/jira/browse/IMPALA-8292 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Critical > > The aim of this ticket to do misc code clean up after Sentry decoupling. For > example, renaming names that contain the word Sentry that may no longer be > applicable, updating comments, etc. -- 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] [Work started] (IMPALA-8281) Implement SHOW GRANT GROUP
[
https://issues.apache.org/jira/browse/IMPALA-8281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-8281 started by Austin Nobis.
> Implement SHOW GRANT GROUP
> --
>
> Key: IMPALA-8281
> URL: https://issues.apache.org/jira/browse/IMPALA-8281
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
>Reporter: Fredy Wijaya
>Assignee: Austin Nobis
>Priority: Critical
>
> Syntax:
> {noformat}
> SHOW GRANT GROUP [ON ]
> {noformat}
> The command is to show list of privileges for a given group with an optional
> ON clause.
--
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] [Assigned] (IMPALA-8281) Implement SHOW GRANT GROUP
[
https://issues.apache.org/jira/browse/IMPALA-8281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Austin Nobis reassigned IMPALA-8281:
Assignee: Austin Nobis
> Implement SHOW GRANT GROUP
> --
>
> Key: IMPALA-8281
> URL: https://issues.apache.org/jira/browse/IMPALA-8281
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
>Reporter: Fredy Wijaya
>Assignee: Austin Nobis
>Priority: Critical
>
> Syntax:
> {noformat}
> SHOW GRANT GROUP [ON ]
> {noformat}
> The command is to show list of privileges for a given group with an optional
> ON clause.
--
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] [Resolved] (IMPALA-8227) Support WITH GRANT OPTION with Ranger authorization provider
[ https://issues.apache.org/jira/browse/IMPALA-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis resolved IMPALA-8227. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Support WITH GRANT OPTION with Ranger authorization provider > > > Key: IMPALA-8227 > URL: https://issues.apache.org/jira/browse/IMPALA-8227 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > This ticket should investigate whether it's feasible to support WITH GRANT > OPTION (giving a grant/revoke privilege for non-admins) with Ranger. If it's > not feasible, Impala should throw an error when Impala is enabled with Ranger. -- 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] [Resolved] (IMPALA-8393) setup-ranger step in create-load-data.sh breaks data load to real clusters
[
https://issues.apache.org/jira/browse/IMPALA-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Austin Nobis resolved IMPALA-8393.
--
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> setup-ranger step in create-load-data.sh breaks data load to real clusters
> --
>
> Key: IMPALA-8393
> URL: https://issues.apache.org/jira/browse/IMPALA-8393
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.2.0, Impala 3.3.0
>Reporter: David Knupp
>Assignee: Austin Nobis
>Priority: Critical
> Fix For: Impala 3.3.0
>
>
> {{localhost}} is hard-coded into the setup-ranger function that was recently
> added to create-load-data.sh, e.g.:
> https://github.com/apache/impala/blame/master/testdata/bin/create-load-data.sh#L325
> This works when testing on a mini-cluster, but breaks data load if setting up
> to run the functional test suite against an actual cluster. In that scenario,
> the host that runs the script is simply a test runner, with no locally
> running services.
--
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] [Work started] (IMPALA-8393) setup-ranger step in create-load-data.sh breaks data load to real clusters
[
https://issues.apache.org/jira/browse/IMPALA-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-8393 started by Austin Nobis.
> setup-ranger step in create-load-data.sh breaks data load to real clusters
> --
>
> Key: IMPALA-8393
> URL: https://issues.apache.org/jira/browse/IMPALA-8393
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.2.0, Impala 3.3.0
>Reporter: David Knupp
>Assignee: Austin Nobis
>Priority: Critical
>
> {{localhost}} is hard-coded into the setup-ranger function that was recently
> added to create-load-data.sh, e.g.:
> https://github.com/apache/impala/blame/master/testdata/bin/create-load-data.sh#L325
> This works when testing on a mini-cluster, but breaks data load if setting up
> to run the functional test suite against an actual cluster. In that scenario,
> the host that runs the script is simply a test runner, with no locally
> running services.
--
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] [Resolved] (IMPALA-8226) Implement GRANT/REVOKE privilege to GROUP
[ https://issues.apache.org/jira/browse/IMPALA-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis resolved IMPALA-8226. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Implement GRANT/REVOKE privilege to GROUP > - > > Key: IMPALA-8226 > URL: https://issues.apache.org/jira/browse/IMPALA-8226 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > Ranger supports granting/revoking a privilege to a group directly. Only admin > should be able to do a grant/revoke. > Syntax: > GRANT ON TO GROUP > REVOKE ON FROM GROUP -- 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] [Work started] (IMPALA-8227) Support WITH GRANT OPTION with Ranger authorization provider
[ https://issues.apache.org/jira/browse/IMPALA-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8227 started by Austin Nobis. > Support WITH GRANT OPTION with Ranger authorization provider > > > Key: IMPALA-8227 > URL: https://issues.apache.org/jira/browse/IMPALA-8227 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Major > > This ticket should investigate whether it's feasible to support WITH GRANT > OPTION (giving a grant/revoke privilege for non-admins) with Ranger. If it's > not feasible, Impala should throw an error when Impala is enabled with Ranger. -- 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] [Assigned] (IMPALA-8309) Use a more human-readable flag to switch to a different authorization provider
[
https://issues.apache.org/jira/browse/IMPALA-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Austin Nobis reassigned IMPALA-8309:
Assignee: radford nguyen (was: Austin Nobis)
> Use a more human-readable flag to switch to a different authorization provider
> --
>
> Key: IMPALA-8309
> URL: https://issues.apache.org/jira/browse/IMPALA-8309
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
>Reporter: Fredy Wijaya
>Assignee: radford nguyen
>Priority: Minor
>
> We currently use authorization_factory_class flag to switch to a different
> authorization provider, which is useful for any third party to provide an
> implementation of authorization provider. Since, Sentry and Ranger are
> officially supported by Impala, we should have a flag, i.e.
> authorization_provider=[sentry|ranger] to easily switch between officially
> supported authorization providers.
> At the time of this writing, the existing {{authorization_factory_class}}
> flag is being retained but its default value removed. If present, it will
> take precedence over the {{authorization_provider}} flag being added.
--
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] [Work started] (IMPALA-8309) Use a more human-readable flag to switch to a different authorization provider
[
https://issues.apache.org/jira/browse/IMPALA-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-8309 started by Austin Nobis.
> Use a more human-readable flag to switch to a different authorization provider
> --
>
> Key: IMPALA-8309
> URL: https://issues.apache.org/jira/browse/IMPALA-8309
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
>Reporter: Fredy Wijaya
>Assignee: Austin Nobis
>Priority: Minor
>
> We currently use authorization_factory_class flag to switch to a different
> authorization provider, which is useful for any third party to provide an
> implementation of authorization provider. Since, Sentry and Ranger are
> officially supported by Impala, we should have a flag, i.e.
> authorization_provider=[sentry|ranger] to easily switch between officially
> supported authorization providers.
> At the time of this writing, the existing {{authorization_factory_class}}
> flag is being retained but its default value removed. If present, it will
> take precedence over the {{authorization_provider}} flag being added.
--
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] [Resolved] (IMPALA-8368) Create database/table with Ranger throws UnsupportedOperationException
[ https://issues.apache.org/jira/browse/IMPALA-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis resolved IMPALA-8368. -- Resolution: Fixed > Create database/table with Ranger throws UnsupportedOperationException > -- > > Key: IMPALA-8368 > URL: https://issues.apache.org/jira/browse/IMPALA-8368 > Project: IMPALA > Issue Type: Sub-task > Components: Frontend >Reporter: Austin Nobis >Assignee: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > When executing *create database ;* in Impala with Ranger enabled, > an *UnsupportedOperationException* will be thrown. -- 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] [Work started] (IMPALA-8368) Create database/table with Ranger throws UnsupportedOperationException
[ https://issues.apache.org/jira/browse/IMPALA-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8368 started by Austin Nobis. > Create database/table with Ranger throws UnsupportedOperationException > -- > > Key: IMPALA-8368 > URL: https://issues.apache.org/jira/browse/IMPALA-8368 > Project: IMPALA > Issue Type: Sub-task > Components: Frontend >Reporter: Austin Nobis >Assignee: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > When executing *create database ;* in Impala with Ranger enabled, a > *UnsupportedOperationException* will be thrown. -- 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-8368) Create database/table with Ranger throws UnsupportedOperationException
[ https://issues.apache.org/jira/browse/IMPALA-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis updated IMPALA-8368: - Description: When executing *create database ;* in Impala with Ranger enabled, an *UnsupportedOperationException* will be thrown. (was: When executing *create database ;* in Impala with Ranger enabled, a *UnsupportedOperationException* will be thrown.) > Create database/table with Ranger throws UnsupportedOperationException > -- > > Key: IMPALA-8368 > URL: https://issues.apache.org/jira/browse/IMPALA-8368 > Project: IMPALA > Issue Type: Sub-task > Components: Frontend >Reporter: Austin Nobis >Assignee: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > When executing *create database ;* in Impala with Ranger enabled, > an *UnsupportedOperationException* will be thrown. -- 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] [Resolved] (IMPALA-8225) Implement GRANT/REVOKE privilege to USER
[
https://issues.apache.org/jira/browse/IMPALA-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Austin Nobis resolved IMPALA-8225.
--
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Implement GRANT/REVOKE privilege to USER
>
>
> Key: IMPALA-8225
> URL: https://issues.apache.org/jira/browse/IMPALA-8225
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
>Reporter: Fredy Wijaya
>Assignee: Austin Nobis
>Priority: Major
> Fix For: Impala 3.3.0
>
>
> Ranger supports granting/revoking a privilege to a user directly. Only admin
> should be able to do a grant/revoke.
> Syntax:
> {noformat}
> GRANT ON TO USER
> REVOKE ON FROM USER
> {noformat}
--
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] [Work started] (IMPALA-8226) Implement GRANT/REVOKE privilege to GROUP
[ https://issues.apache.org/jira/browse/IMPALA-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8226 started by Austin Nobis. > Implement GRANT/REVOKE privilege to GROUP > - > > Key: IMPALA-8226 > URL: https://issues.apache.org/jira/browse/IMPALA-8226 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Major > > Ranger supports granting/revoking a privilege to a group directly. Only admin > should be able to do a grant/revoke. > Syntax: > GRANT ON TO GROUP > REVOKE ON FROM GROUP -- 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] [Assigned] (IMPALA-8226) Implement GRANT/REVOKE privilege to GROUP
[ https://issues.apache.org/jira/browse/IMPALA-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis reassigned IMPALA-8226: Assignee: Austin Nobis > Implement GRANT/REVOKE privilege to GROUP > - > > Key: IMPALA-8226 > URL: https://issues.apache.org/jira/browse/IMPALA-8226 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Major > > Ranger supports granting/revoking a privilege to a group directly. Only admin > should be able to do a grant/revoke. > Syntax: > GRANT ON TO GROUP > REVOKE ON FROM GROUP -- 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] [Resolved] (IMPALA-7918) Remove support for authorization policy file
[ https://issues.apache.org/jira/browse/IMPALA-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis resolved IMPALA-7918. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Remove support for authorization policy file > > > Key: IMPALA-7918 > URL: https://issues.apache.org/jira/browse/IMPALA-7918 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Affects Versions: Impala 3.2.0 >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > Support for authorization policy file has been deprecated in Impala and it > does not work with object ownership. Furthermore, authorization policy file > is very specific to Sentry. Supporting authorization policy will make it > difficult to create a generic authorization framework in Impala. Hence, the > task will involve removing support for authorization policy file. -- 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] [Work started] (IMPALA-7918) Remove support for authorization policy file
[ https://issues.apache.org/jira/browse/IMPALA-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7918 started by Austin Nobis. > Remove support for authorization policy file > > > Key: IMPALA-7918 > URL: https://issues.apache.org/jira/browse/IMPALA-7918 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Affects Versions: Impala 3.2.0 >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Major > > Support for authorization policy file has been deprecated in Impala and it > does not work with object ownership. Furthermore, authorization policy file > is very specific to Sentry. Supporting authorization policy will make it > difficult to create a generic authorization framework in Impala. Hence, the > task will involve removing support for authorization policy file. -- 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] [Assigned] (IMPALA-8225) Implement GRANT/REVOKE privilege to USER
[
https://issues.apache.org/jira/browse/IMPALA-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Austin Nobis reassigned IMPALA-8225:
Assignee: Austin Nobis
> Implement GRANT/REVOKE privilege to USER
>
>
> Key: IMPALA-8225
> URL: https://issues.apache.org/jira/browse/IMPALA-8225
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
>Reporter: Fredy Wijaya
>Assignee: Austin Nobis
>Priority: Major
>
> Ranger supports granting/revoking a privilege to a user directly. Only admin
> should be able to do a grant/revoke.
> Syntax:
> {noformat}
> GRANT ON TO USER
> REVOKE ON FROM USER
> {noformat}
--
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] [Work started] (IMPALA-8225) Implement GRANT/REVOKE privilege to USER
[
https://issues.apache.org/jira/browse/IMPALA-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-8225 started by Austin Nobis.
> Implement GRANT/REVOKE privilege to USER
>
>
> Key: IMPALA-8225
> URL: https://issues.apache.org/jira/browse/IMPALA-8225
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
>Reporter: Fredy Wijaya
>Assignee: Austin Nobis
>Priority: Major
>
> Ranger supports granting/revoking a privilege to a user directly. Only admin
> should be able to do a grant/revoke.
> Syntax:
> {noformat}
> GRANT ON TO USER
> REVOKE ON FROM USER
> {noformat}
--
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] [Resolved] (IMPALA-8328) Add missing ToSql test cases for authorization statements
[ https://issues.apache.org/jira/browse/IMPALA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis resolved IMPALA-8328. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Add missing ToSql test cases for authorization statements > - > > Key: IMPALA-8328 > URL: https://issues.apache.org/jira/browse/IMPALA-8328 > Project: IMPALA > Issue Type: Improvement > Components: Infrastructure >Affects Versions: Impala 3.0, Impala 2.12.0 >Reporter: Austin Nobis >Assignee: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > The following authorization statements are missing tests in the ToSql test > class. > * GrantRevokePrivStmt > * GrantRevokeRoleStmt > * ShowGrantPrincipalStmt > * ShowRolesStmt -- 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] [Resolved] (IMPALA-8326) Incorrect toSql for CreateDropRoleStmt
[ https://issues.apache.org/jira/browse/IMPALA-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis resolved IMPALA-8326. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Incorrect toSql for CreateDropRoleStmt > -- > > Key: IMPALA-8326 > URL: https://issues.apache.org/jira/browse/IMPALA-8326 > Project: IMPALA > Issue Type: Bug > Components: Frontend >Affects Versions: Impala 3.0, Impala 2.12.0 >Reporter: Austin Nobis >Assignee: Austin Nobis >Priority: Major > Fix For: Impala 3.3.0 > > > The toSql method for CreateDropRoleStmt is incorrect. The role name and the > action are in an incorrect order: > Ideal: "create role test_role" > Current: "test_role create role" -- 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-8328) Add missing ToSql test cases for authorization statements
[ https://issues.apache.org/jira/browse/IMPALA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis updated IMPALA-8328: - Component/s: Infrastructure > Add missing ToSql test cases for authorization statements > - > > Key: IMPALA-8328 > URL: https://issues.apache.org/jira/browse/IMPALA-8328 > Project: IMPALA > Issue Type: Improvement > Components: Infrastructure >Reporter: Austin Nobis >Priority: Major > > The following authorization statements are missing tests in the ToSql test > class. > * GrantRevokePrivStmt > * GrantRevokeRoleStmt > * ShowGrantPrincipalStmt > * ShowRolesStmt -- 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] [Assigned] (IMPALA-8328) Add missing ToSql test cases for authorization statements
[ https://issues.apache.org/jira/browse/IMPALA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis reassigned IMPALA-8328: Assignee: Austin Nobis > Add missing ToSql test cases for authorization statements > - > > Key: IMPALA-8328 > URL: https://issues.apache.org/jira/browse/IMPALA-8328 > Project: IMPALA > Issue Type: Improvement > Components: Infrastructure >Reporter: Austin Nobis >Assignee: Austin Nobis >Priority: Major > > The following authorization statements are missing tests in the ToSql test > class. > * GrantRevokePrivStmt > * GrantRevokeRoleStmt > * ShowGrantPrincipalStmt > * ShowRolesStmt -- 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] [Created] (IMPALA-8328) Add missing ToSql test cases for authorization statements
Austin Nobis created IMPALA-8328: Summary: Add missing ToSql test cases for authorization statements Key: IMPALA-8328 URL: https://issues.apache.org/jira/browse/IMPALA-8328 Project: IMPALA Issue Type: Improvement Reporter: Austin Nobis The following authorization statements are missing tests in the ToSql test class. * GrantRevokePrivStmt * GrantRevokeRoleStmt * ShowGrantPrincipalStmt * ShowRolesStmt -- 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] [Created] (IMPALA-8326) Incorrect toSql for CreateDropRoleStmt
Austin Nobis created IMPALA-8326: Summary: Incorrect toSql for CreateDropRoleStmt Key: IMPALA-8326 URL: https://issues.apache.org/jira/browse/IMPALA-8326 Project: IMPALA Issue Type: Bug Components: Frontend Reporter: Austin Nobis Assignee: Austin Nobis The toSql method for CreateDropRoleStmt is incorrect. The role name and the action are in an incorrect order: Ideal: "create role test_role" Current: "test_role create role" -- 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] [Assigned] (IMPALA-7918) Remove support for authorization policy file
[ https://issues.apache.org/jira/browse/IMPALA-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Nobis reassigned IMPALA-7918: Assignee: Austin Nobis > Remove support for authorization policy file > > > Key: IMPALA-7918 > URL: https://issues.apache.org/jira/browse/IMPALA-7918 > Project: IMPALA > Issue Type: Sub-task > Components: Catalog, Frontend >Affects Versions: Impala 3.2.0 >Reporter: Fredy Wijaya >Assignee: Austin Nobis >Priority: Major > > Support for authorization policy file has been deprecated in Impala and it > does not work with object ownership. Furthermore, authorization policy file > is very specific to Sentry. Supporting authorization policy will make it > difficult to create a generic authorization framework in Impala. Hence, the > task will involve removing support for authorization policy file. -- 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
