[
https://issues.apache.org/jira/browse/PHOENIX-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500489#comment-14500489
]
James Taylor commented on PHOENIX-1682:
---------------------------------------
I see - HBase restricts the characters that may be used for a table name, so I
think "." wouldn't be allowed. For a VIEW, which doesn't map to an HBase table,
we'd likely allow it. For looking up the table in the cache, we don't separated
the schema and table name. If it's not found, we do, but I think in the end,
the schema and table name just get put back together again, so it'd likely just
work. It's worth a test case, though.
> 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)
