[
https://issues.apache.org/jira/browse/PHOENIX-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614468#comment-14614468
]
maghamravikiran commented on PHOENIX-2036:
------------------------------------------
[~jmahonin]
Consider the following cases which are likely to fail due to escaping the
table name argument in the PhoenixRDD.
a) User passes a quote encoded table name.
b) Assuming a fullTableName in the format CUSTOM_ENTITY."z02" .
I prefer to keep the onus of passing the table name with the quote encoding on
the user. So in the case of tests, the table name should be encoded in the
tests itself. My two cents.
> PhoenixConfigurationUtil should provide a pre-normalize table name to
> PhoenixRuntime
> ------------------------------------------------------------------------------------
>
> Key: PHOENIX-2036
> URL: https://issues.apache.org/jira/browse/PHOENIX-2036
> Project: Phoenix
> Issue Type: Bug
> Reporter: Siddhi Mehta
> Assignee: maghamravikiran
> Priority: Minor
> Attachments: PHOENIX-2036-spark.patch, PHOENIX-2036-v1.patch,
> PHOENIX-2036-v1.patch, PHOENIX-2036-v2.patch, PHOENIX-2036.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I was trying a basic store using PhoenixHBaseStorage and ran into some issues
> with it complaining about TableNotFoundException.
> The table(CUSTOM_ENTITY."z02") in question exists.
> Looking at the stacktrace I think its likely related to the change in
> PHOENIX-1682 where phoenix runtime expects a pre-normalized table name.
> We need to update
> PhoenixConfigurationUtil.getSelectColumnMetadataList(Configuration) be pass a
> pre-normalized table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
