[
https://issues.apache.org/jira/browse/TRAFODION-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063256#comment-16063256
]
Roberta Marton commented on TRAFODION-2175:
-------------------------------------------
Added support for - delivered on <June 26>:
get schemas (in catalog)
get tables, indexes (in schema)
get sequences, views (in schema, in catalog)
get libraries, procedures, functions, table mapping functions
The following statements still need to be changed:
get catalogs
get indexes on table
get procedures for library
get objects in query
get views on object
get schemas for <user/role>
get hive registered objects, schemas, tables, views in catalog
get hive external tables in catalog
get hbase objects, tables in catalog
> a user should only see specific schemas/tables that he has privileges to
> ------------------------------------------------------------------------
>
> Key: TRAFODION-2175
> URL: https://issues.apache.org/jira/browse/TRAFODION-2175
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-security
> Environment: OS -- centos6.7 , centos7.1 , centos7.2
> esgynDB -- R2.2 daily build
> Reporter: Gao, Rui-Xian
> Assignee: Roberta Marton
>
> we have a requirement that a user should only see the objects that he has
> privileges to do operations on.
> Current feature is, ‘get schemas’ will return all schemas in the database,
> and in a private schema created by a user, another user can still see all
> tables with ‘get tables’, and also can check table’s structure with ‘showddl’.
>
> If we have many customer data on cloud cluster, we don’t want a customer to
> view any other customers’ data, we want the customers to be isolated from
> each other.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
