[
https://issues.apache.org/jira/browse/KUDU-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277997#comment-15277997
]
Adar Dembo commented on KUDU-981:
---------------------------------
I was also wondering where exactly we should draw the line on this. The Impala
rules are certainly a coherent set of restrictions, but aren't they what they
are because identifiers are embedded in SQL queries, which places additional
restrictions on them? Kudu doesn't have that problem, though Kudu tables do
need to be usable within Impala. What happens if I try to use a Kudu table
whose name is prohibited by the Impala identifier rules in Impala? Does CREATE
EXTERNAL TABLE fail?
If nothing else, I'd prefer a set of rules that's more predictable and
discoverable, and the Impala identifier rules aren't that. For example, 128
characters seems like a totally arbitrary length limit.
> Validate table and column names
> -------------------------------
>
> Key: KUDU-981
> URL: https://issues.apache.org/jira/browse/KUDU-981
> Project: Kudu
> Issue Type: Bug
> Components: master
> Affects Versions: Private Beta
> Reporter: Todd Lipcon
> Priority: Critical
> Attachments: naming-freedom.png
>
>
> Currently I believe we allow table names such as "", " ", etc. We should
> probably figure out a reasonable subset of characters and validate names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
