[
https://issues.apache.org/jira/browse/PHOENIX-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497164#comment-14497164
]
Ivan Weiss commented on PHOENIX-1682:
-------------------------------------
[~giacomotaylor] I was told to ask you about the proper way to deal with
various Schema/Table/Case Sensitive situations. Currently we are normalizing
and stripping the quotes off of case sensitive table names but we normalize
when there is a leading schema name
Please tell me which of these is valid, invalid or needs correction:
TableName becomes TABLENAME
"TableName" becomes TableName
SchemaName.TableName becomes SCHEMANAME & TABLENAME
SchemaName."TableName" becomes SCHEMANAME & TableName
"SchemaName"."TableName" becomes SchemaName & TableName
"Schema.Name"."TableName" becomes Schema.Name & TableName
> PhoenixRuntime.getTable() does not work with case-sensitive table names
> -----------------------------------------------------------------------
>
> Key: PHOENIX-1682
> URL: https://issues.apache.org/jira/browse/PHOENIX-1682
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: Eli Levine
> Assignee: Ivan Weiss
> Labels: Newbie
>
> PhoenixRuntime.getTable(conn, name) assumes _name_ is a single component
> because it calls SchemaUtil.normalizeIdentifier(name) on the whole thing,
> without breaking up _name_ into table name and schema name components. In
> cases where a table is case sensitive (created with _schemaName."tableName"_)
> this will result in getTable not finding the table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
