phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4623) Inconsistent physical view index name
Date Mon, 07 May 2018 20:07:00 GMT

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

Thomas D'Silva commented on PHOENIX-4623:
-----------------------------------------

In phoenix its called from a test which we can change to use MetaDataUtil.getIndexPhysicalName().
Any clients that call MetaDataUtil.getViewIndexName need to be modified to use MetaDataUtil.getIndexPhysicalName()
instead. We should just remove  getViewIndexName(). 

> 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)

Mime
View raw message