[
https://issues.apache.org/jira/browse/KUDU-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495776#comment-16495776
]
Thomas Tauber-Marshall commented on KUDU-2459:
----------------------------------------------
Definitely in favor of using a placeholder name instead of trying to derive a
valid name, since the derivation could result in surprising/unintuitive results.
A possible compromise would be to only show the placeholder for table names
where we know that the name isn't valid, so if the name is a valid Impala name
its still just a copy-paste, which I assume is the common case. You'd have to
be careful about verifying the validity though - in addition to no dots, we
have several other requirement, see:
http://impala.apache.org/docs/build3x/html/topics/impala_identifiers.html
> Impala 'Create Table' Statement under Web UI doesn't account for non-Impala
> conforming tablenames
> -------------------------------------------------------------------------------------------------
>
> Key: KUDU-2459
> URL: https://issues.apache.org/jira/browse/KUDU-2459
> Project: Kudu
> Issue Type: Bug
> Components: ui
> Affects Versions: 1.7.0
> Reporter: Shriya Gupta
> Assignee: Shriya Gupta
> Priority: Major
> Attachments: Screen Shot 2018-05-30 at 4.45.12 PM.png
>
>
> Under the Tables section of Kudu Web UI, for a selected table, the table
> metrics display a CREATE TABLE statement that can be run to make Impala
> cognizant of that table. However, in generation of this statement, the table
> name tries to match the original Kudu tablename which may not always be
> acceptable as a tablename for Impala. For example, Kudu accepts dot in
> tablename, Impala does not.
> A statement like the following throws an invalid tablename error in Impala –
> !Screen Shot 2018-05-30 at 4.45.12 PM.png|width=606,height=321!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
