hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "He Yongqiang (JIRA)" <>
Subject [jira] Commented: (HIVE-78) Authorization infrastructure for Hive
Date Tue, 14 Dec 2010 23:06:06 GMT


He Yongqiang commented on HIVE-78:

By "If you want, do follow ups on them." I meant "if you want, open follow up jiras and assign
to me"

Here are some points that why they are not easy to do:
For JDO embedding,
Mostly in the new Objects, there are Table object, Database object, Partition object.

If we only keep name for them, It's ok for database. But for Table, need to user dbName, tableName,
For partition need dbName, tableName, partName.
And need to fetch the object on client side to see the object exist or not. And pass the names
to meta-store, the metastore will do another lookup to find ids for db/tbl/part to put into
new objects.

For thrift apis, one benefit of consolidating into one is reducing the api numbers. 

> Authorization infrastructure for Hive
> -------------------------------------
>                 Key: HIVE-78
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore, Query Processor, Server Infrastructure
>            Reporter: Ashish Thusoo
>            Assignee: He Yongqiang
>         Attachments: createuser-v1.patch, hive-78-metadata-v1.patch, hive-78-syntax-v1.patch,
HIVE-78.1.nothrift.patch, HIVE-78.1.thrift.patch, HIVE-78.2.nothrift.patch, HIVE-78.2.thrift.patch,
HIVE-78.4.complete.patch, HIVE-78.4.no_thrift.patch, HIVE-78.5.complete.patch, HIVE-78.5.no_thrift.patch,
HIVE-78.6.complete.patch, HIVE-78.6.no_thrift.patch, HIVE-78.7.no_thrift.patch, HIVE-78.7.patch,
> Allow hive to integrate with existing user repositories for authentication and authorization

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message