[
https://issues.apache.org/jira/browse/HCATALOG-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094967#comment-13094967
]
Alan Gates commented on HCATALOG-89:
------------------------------------
According to [the
design|https://cwiki.apache.org/HCATALOG/hcatalog-hbase-integration-design.html],
the plan is to switch HCat's security to use Hive's HiveAuthorizationProvider
interface. Then behind that we can implement an HBase specific handler and an
HDFS specific one. This patch instead is disabling security checks for HBase.
Has the plan changed, or is this just a short cut for testing purposes until
the security changes are made? I'm ok with this as a short cut; I'm not ok
with it as an alternate implementation.
> Support for creating non-native tables
> --------------------------------------
>
> Key: HCATALOG-89
> URL: https://issues.apache.org/jira/browse/HCATALOG-89
> Project: HCatalog
> Issue Type: New Feature
> Reporter: Vandana Ayyalasomayajula
> Assignee: Vandana Ayyalasomayajula
> Labels: HBase, Tables
> Attachments: HCATALOG-89.patch
>
>
> HCatalog CLI currently does not support the "STORED BY" token from HIVE,
> which is used to create non-native tables (for example in HBase). This
> feature will help users in creating HBase tables and then enable them to
> read/write to those tables using the HBase storage handler.
> In addition, the "CreateTableHook" during the post analysis phase (
> "postAnalyze" method ) checks for authorization to create table. This
> authorization would fail as there is no native table for tables created by
> "STORED BY" tokens. The "postAnalyze" method should first check if there
> exists a storage handler for the DDL task, if yes, then it should not call
> the "authorize" method. In future, this authorization process should be
> pushed to the storage handlers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
