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

Hudson commented on PHOENIX-5456:
---------------------------------

SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.5 #127 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.5/127/])
PHOENIX-5456 IndexScrutinyTool slow for indexes on multitenant tables (kadir: 
rev 22afe64e1bc37455627b9633f4fd31362f6de485)
* (add) 
phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexScrutinyToolForTenantIT.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/util/IndexColumnNames.java
* (add) 
phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexScrutinyToolBaseIT.java
* (edit) 
phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexScrutinyToolIT.java


> IndexScrutinyTool slow for indexes on multitenant tables
> --------------------------------------------------------
>
>                 Key: PHOENIX-5456
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5456
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.0, 5.1.0
>            Reporter: Vincent Poon
>            Assignee: Gokcen Iskender
>            Priority: Major
>         Attachments: PHOENIX-5456.4.x-1.3.1.patch, 
> PHOENIX-5456.master.1.patch, PHOENIX-5456.master.2.patch
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The IndexScrutinyTool is doing full scans for index tables on multitenant 
> tables. 
> This is due to a change in PHOENIX-5089, where we added code to 
> IndexColumnNames to skip a portion of the PK if the table is multitenant:
> https://github.com/apache/phoenix/commit/cc9754fff840f38d13c3adb0c963296959fff3fa#diff-0705645faa779229d00792c032ed377fR64
> This causes scrutinies for global, non-view indexes on multitenant tables to 
> skip the tenantId when generating the pk column list, thereby causing a full 
> scan.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to