[
https://issues.apache.org/jira/browse/HCATALOG-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204089#comment-13204089
]
Ashutosh Chauhan commented on HCATALOG-245:
-------------------------------------------
This is leading to leaky abstraction. We should enhance AuthProvider interface
if its in current form its not sufficient. There are two concerns I have as
such in current implementation:
* We are still doing all the checks in HCatalog Client, so using that interface
is not really of much use.
* It introduces Hive internal Datastructures like DDLTask, DDLWork,
CreateTableDesc etc. into HCatalog, which if possible we should avoid to
maintain code modularity.
> StorageHandler authorization providers
> ---------------------------------------
>
> Key: HCATALOG-245
> URL: https://issues.apache.org/jira/browse/HCATALOG-245
> Project: HCatalog
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Attachments: hcat-auth_v1.patch
>
>
> As per the design in the parent issue, we will delegate the authorization
> checks to the storage handler (hdfs is considered as a storage handler as
> well). This jira will introduce HiveAuthorizationProviders for hbase + hdfs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
