You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/08/05 23:22:20 UTC

[jira] [Commented] (KUDU-1119) Consider supporting Impala tablespaces for Kudu tables

    [ https://issues.apache.org/jira/browse/KUDU-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410271#comment-15410271 ] 

Todd Lipcon commented on KUDU-1119:
-----------------------------------

I think we should consider prioritizing this sooner rather than later, for two reasons:
(1) will simplify users trying to map Hive/Impala tables to Kudu tables
(2) will be critical for security policies at a later date, so that a user can be given permission to create/drop their own tables.

> Consider supporting Impala tablespaces for Kudu tables
> ------------------------------------------------------
>
>                 Key: KUDU-1119
>                 URL: https://issues.apache.org/jira/browse/KUDU-1119
>             Project: Kudu
>          Issue Type: Improvement
>          Components: impala
>    Affects Versions: Public beta
>            Reporter: Misty Stanley-Jones
>
> Right now if you create a table using Impala, in a given Impala database (my_database:my_table), Kudu strips out the database part and just calls the table my_table. This creates a requirement for Kudu table names to be unique across all Impala databases, and may be surprising behavior to seasoned Impala users. I'm filing this ticket at [~tlipcon]'s request and may be getting some of the details / limitations wrong.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)