[ https://issues.apache.org/jira/browse/PHOENIX-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372211#comment-16372211 ]
Akshita Malhotra commented on PHOENIX-4623: ------------------------------------------- [~jamestaylor] As per an offline discussion with [~tdsilva], seems to be a naming bug during creation of physical view index table unless it was intended which doesn't seem plausible . A simple bug fix would be to modify the getViewIndexName API to return "_IDX_SCH.TABLE" Due to this Hgrate is not correctly identifying the physical view indexes. What could be other implications of this? > 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.14.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)