phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-5089) IndexScrutinyTool should be able to analyze tenant-owned indexes
Date Wed, 01 May 2019 04:30:00 GMT

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

Thomas D'Silva updated PHOENIX-5089:
------------------------------------
    Fix Version/s:     (was: 5.1)
                   5.1.0

> 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
>             Fix For: 4.15.0, 5.1.0
>
>         Attachments: PHOENIX-5089-4x-1.4.patch, PHOENIX-5089.patch
>
>          Time Spent: 2h 40m
>  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)

Mime
View raw message