[
https://issues.apache.org/jira/browse/PHOENIX-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616051#comment-14616051
]
Hudson commented on PHOENIX-2036:
---------------------------------
FAILURE: Integrated in Phoenix-master #814 (See
[https://builds.apache.org/job/Phoenix-master/814/])
PHOENIX-2036 PhoenixConfigurationUtil should provide a pre-normalize table name
to PhoenixRuntime (jmahonin: rev 39c982f923033b97c477464d0c4e27221421774d)
* phoenix-spark/src/it/scala/org/apache/phoenix/spark/PhoenixSparkIT.scala
* phoenix-spark/src/main/scala/org/apache/phoenix/spark/PhoenixRDD.scala
* phoenix-spark/src/it/resources/setup.sql
> 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-v2.patch, 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)
