[
https://issues.apache.org/jira/browse/IMPALA-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831076#comment-16831076
]
ASF subversion and git services commented on IMPALA-5351:
---------------------------------------------------------
Commit b4ff8018d33c71a502b3184d2f8ffb6c5e6c0207 in impala's branch
refs/heads/master from Thomas Tauber-Marshall
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b4ff801 ]
Bump Kudu version to 9ba901a
This pulls in the new API for column comments needed for IMPALA-5351.
Change-Id: I2b6d70908e133eacb01ec3b9616d8361db3417a2
Reviewed-on: http://gerrit.cloudera.org:8080/13197
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Handle column comments for Kudu tables
> --------------------------------------
>
> Key: IMPALA-5351
> URL: https://issues.apache.org/jira/browse/IMPALA-5351
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 2.9.0
> Reporter: Thomas Tauber-Marshall
> Assignee: HeLifu
> Priority: Major
> Labels: kudu
>
> Currently, if a column comment is specified in a CREATE TABLE for a Kudu
> table, we just silently drop it because Kudu does not currently support
> column comments (KUDU-1711).
> One option would be to store the comments in HMS, but splitting the metadata
> between HMS and Kudu is probably more complicated than its worth.
> Most likely, we can just wait for it to be implemented on the Kudu side, but
> before then we may want to consider issuing a warning when people use column
> comments on Kudu tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
