phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Mahonin (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-2036) PhoenixConfigurationUtil should provide a pre-normalize table name to PhoenixRuntime
Date Mon, 06 Jul 2015 14:43:05 GMT


Josh Mahonin updated PHOENIX-2036:
    Attachment: PHOENIX-2036-spark-v2.patch

Use Phoenix helper where possible for escaping in phoenix-spark

Remove the 'buildSql' helpers and use the PhoenixConfigurationUtil / PhoenixConfiguration

Add a unit test to make sure we can load tables with schemas and escaped table names.

NOTE: This may have merge conflicts with the patch in PHOENIX-2088. I can adjust this one,
or that one, where necessary.

> PhoenixConfigurationUtil should provide a pre-normalize table name to PhoenixRuntime
> ------------------------------------------------------------------------------------
>                 Key: PHOENIX-2036
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message