You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/05/07 00:58:00 UTC

[jira] [Resolved] (IMPALA-3193) Return table comments in GetTables Thrift API call and SHOW TABLES statement resultset

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

Tim Armstrong resolved IMPALA-3193.
-----------------------------------
    Resolution: Duplicate

> Return table comments in GetTables Thrift API call and SHOW TABLES statement resultset
> --------------------------------------------------------------------------------------
>
>                 Key: IMPALA-3193
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3193
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog, Clients
>    Affects Versions: Impala 1.3, Impala 1.4, Impala 2.0, Impala 2.1, Impala 2.2
>            Reporter: Holman Lan
>            Assignee: Jinchul Kim
>            Priority: Minor
>              Labels: ramp-up
>         Attachments: SimpleTestApp.java
>
>
> When accessing Impala via the Thrift interface the server always returns empty string for the comments/remarks column for the GetTables API call.
> It would also be nice if Impala can return table comments for the SHOW TABLES statement. Currently it only returns the table name.
> Attached is a simple Java program that uses the open-source Hive JDBC driver to connect to Impala via the Thrift interface and prints out results for the getTables JDBC API call. We notice that the JDBC driver internally uses the GetTables API call to retrieve metadata from Impala for the getTables JDBC API call. The remarks/comments column is always an empty string and it looks like it is because the server always returns empty string for that column.
> Impala returns column comments for the GetColumns Thrift API call as well as the DESCRIBE <table> statement.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)