phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4623) Inconsistent physical view index name
Date Fri, 04 May 2018 16:08:00 GMT


Thomas D'Silva commented on PHOENIX-4623:

I don't think its a blocker for the release, because we have a workaround to use MetadataUtil.

getViewIndexPhysicalName(byte[] physicalTableName) .

> Inconsistent physical view index name
> -------------------------------------
>                 Key: PHOENIX-4623
>                 URL:
>             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
> 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

View raw message