phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-2036) PhoenixConfigurationUtil should provide a pre-normalize table name to PhoenixRuntime
Date Mon, 22 Aug 2016 00:31:20 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser updated PHOENIX-2036:
--------------------------------
    Fix Version/s: 4.5.0

> 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
>             Fix For: 4.5.0
>
>         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)

Mime
View raw message