[
https://issues.apache.org/jira/browse/PHOENIX-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462964#comment-16462964
]
Thomas D'Silva commented on PHOENIX-4623:
-----------------------------------------
[~jamestaylor]
We have a bug in MetaDataUtil.getIndexPhysicalName. It returns the correctly
physical name when namespaces are enabled eg. "SCH:_IDX_TABLE" but when
namespaces are not enabled and the table has a schema it returns
"_IDX_SCH.TABLE". This is the table name used to create the view index table
for existing clusters.
MetaDataUtil.getViewIndexName returns "SCH._IDX_TABLE" which is not the name
that was used to create the view index table.
We can fix MetaDataUtil.getIndexPhysicalName to return the "SCH._IDX_TABLE" ,
but we would also have to rename the existing view index tables (by taking a
snapshot).
Or we could just change MetaDataUtil.getViewIndexName to return
"_IDX_SCH.TABLE". WDYT?
> Inconsistent physical view index name
> -------------------------------------
>
> Key: PHOENIX-4623
> URL: https://issues.apache.org/jira/browse/PHOENIX-4623
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.13.0
> Reporter: Akshita Malhotra
> Priority: Major
> Labels: easyfix
> Fix For: 4.15.0
>
>
> The physical view indexes are incorrectly named when table has a schema. For
> instance, if a table name is "SCH.TABLE", during creation the physical index
> table is named as "_IDX_SCH.TABLE" which doesn't look right. In case
> namespaces are enabled, the physical index table is named as "SCH:_IDX_TABLE"
> The client APIs on the other hand such as
> MetaDataUtil.getViewIndexName(String schemaName, String tableName) API to
> retrieve the phyisical view index name returns "SCH._IDX_TABLE" which as per
> convention returns the right name but functionally leads to wrong results as
> this is not how the physical indexes are named during construction.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
