phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2036) PhoenixConfigurationUtil should provide a pre-normalize table name to PhoenixRuntime
Date Tue, 16 Jun 2015 02:29:01 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587352#comment-14587352
] 

James Taylor commented on PHOENIX-2036:
---------------------------------------

Thanks for the quick turnaround, [~maghamravikiran]. Would it be possible to add some tests
around case sensitive and case insensitive names? I think it'll help us ensure we're all on
the same page.

> 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
>            Priority: Minor
>         Attachments: 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