[
https://issues.apache.org/jira/browse/PHOENIX-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605866#comment-14605866
]
James Taylor commented on PHOENIX-2036:
---------------------------------------
FYI, [~tdsilva] is working on a change that may or may not help here. We've
found that at least with the list of column names, there's no need to parse
them and then re-combine them, as this is problematic as there's no good
character to use as a separator. The reason is that with functional indexes, it
may not just be a column name, but can be any expression (which, of course, can
use any character within a quoted string).
Instead, Thomas is going to just have the expressions be comma separated and
use the entire string to form the SELECT statement. Do you foresee any issues
with this, [~maghamravi]?
> 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-v1.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)
