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

Posted to dev@phoenix.apache.org by "Gokcen Iskender (JIRA)" <ji...@apache.org> on 2019/02/15 22:41:00 UTC

[jira] [Updated] (PHOENIX-5089) IndexScrutinyTool should be able to analyze tenant-owned indexes

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

Gokcen Iskender updated PHOENIX-5089:
-------------------------------------
    Attachment: PHOENIX-5089.patch

> IndexScrutinyTool should be able to analyze tenant-owned indexes
> ----------------------------------------------------------------
>
>                 Key: PHOENIX-5089
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5089
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Geoffrey Jacoby
>            Assignee: Gokcen Iskender
>            Priority: Major
>         Attachments: PHOENIX-5089.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> IndexScrutiny uses global connections to lookup the indexes which it's asked to analyze, which means that it won't be able to see indexes owned by tenant views. We should add an optional tenantId parameter to it that will use a tenant connection (and potentially our MapReduce framework's tenant connection support) to allow for analyzing those indexes as well.
> This is similar to PHOENIX-4940 for the index rebuild tool.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)