[
https://issues.apache.org/jira/browse/KUDU-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao updated KUDU-2973:
--------------------------
Description: For Ranger integration, we need to continue to have
semi-database support. And currently it is tied to the HMS integration, which
needs to be separated out. This includes to extract database information from
table name for retrieving corresponding Ranger policies. For example,
"db.table" belongs to 'db'. And as Kudu table name is case sensitive and can
have special character, database "table" will be considered as 'table' that
belongs to 'default' database, and "db.table.abc" will be considered as
'table.abc' that belongs to 'db' database. (was: For Ranger integration, we
need to continue to have semi-database support. And currently it is tied to the
HMS integration, which needs to be separated out.)
> Support semi-database concept even without HMS integration
> ----------------------------------------------------------
>
> Key: KUDU-2973
> URL: https://issues.apache.org/jira/browse/KUDU-2973
> Project: Kudu
> Issue Type: Sub-task
> Affects Versions: 1.11.0
> Reporter: Hao Hao
> Assignee: Attila Bukor
> Priority: Major
>
> For Ranger integration, we need to continue to have semi-database support.
> And currently it is tied to the HMS integration, which needs to be separated
> out. This includes to extract database information from table name for
> retrieving corresponding Ranger policies. For example, "db.table" belongs to
> 'db'. And as Kudu table name is case sensitive and can have special
> character, database "table" will be considered as 'table' that belongs to
> 'default' database, and "db.table.abc" will be considered as 'table.abc' that
> belongs to 'db' database.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
