You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2019/12/10 18:14:00 UTC

[jira] [Updated] (PHOENIX-5456) IndexScrutinyTool slow for indexes on multitenant tables

     [ https://issues.apache.org/jira/browse/PHOENIX-5456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Jacoby updated PHOENIX-5456:
-------------------------------------
    Fix Version/s: 4.15.0
                   5.10

> 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
>             Fix For: 4.15.0, 5.10
>
>         Attachments: PHOENIX-5456.4.x-1.3.1.patch, PHOENIX-5456.master.1.patch, PHOENIX-5456.master.2.patch
>
>          Time Spent: 1h
>  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.4#803005)