You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2016/08/17 23:15:21 UTC

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

     [ https://issues.apache.org/jira/browse/KUDU-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Serbin reassigned KUDU-1119:
-----------------------------------

    Assignee: Alexey Serbin

> 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
>            Assignee: Alexey Serbin
>
> 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)