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

Hudson commented on PHOENIX-4623:
---------------------------------

ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1882 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1882/])
PHOENIX-4623 Inconsistent physical view index name (jtaylor: rev 
78e94f7c745239730b17117b32b7505ce86bb54a)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/BaseViewIT.java
* (edit) 
phoenix-core/src/it/java/org/apache/phoenix/schema/stats/StatsCollectorIT.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/ViewIT.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/UpgradeUtil.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/MetaDataUtil.java


> 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
>            Assignee: James Taylor
>            Priority: Major
>              Labels: easyfix
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4623_v1.patch
>
>
> 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)

Reply via email to