Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce number of options for Access Control Type #153

Open
AnanaMJ opened this issue Feb 7, 2019 · 0 comments
Open

Reduce number of options for Access Control Type #153

AnanaMJ opened this issue Feb 7, 2019 · 0 comments

Comments

@AnanaMJ
Copy link
Contributor

AnanaMJ commented Feb 7, 2019

As a developer
I'd like to have only READ_ONLY, READ_AND_WRITE and READ_WRITE_AND_CREATE as access control type options
As to have a more intuitive behaviour of the configuration


The complete current options are READ_ONLY, READ_AND_WRITE_AND_CREATE, READ_AND_WRITE_AND_CREATE_ON_DATABASE_WHITELIST and READ_AND_WRITE_ON_DATABASE_WHITELIST.

However (from documentation):

Primary metastores can configure access-control-type to have any of the described access-control-types whereas federated metastores may only be configured to READ_ONLY and READ_AND_WRITE_ON_DATABASE_WHITELIST.

Changing the functionality to replace READ_AND_WRITE_AND_CREATE_ON_DATABASE_WHITELIST with READ_AND_WRITE_AND_CREATE and rename READ_AND_WRITE_ON_DATABASE_WHITELIST to READ_AND_WRITE might make the behaviour more intuitive. The difference would be that the primary metastore would not be able to create databases without adding them into the primary-meta-store.writable-database-white-list property, and writing would only be allowed to be done on databases in the whitelist for both types of metastores.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant