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

Posted to dev@phoenix.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2019/02/11 23:12:00 UTC

[jira] [Resolved] (PHOENIX-4940) IndexTool should be able to rebuild tenant-owned indexes

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

Josh Elser resolved PHOENIX-4940.
---------------------------------
    Resolution: Fixed

Sorry, looks like an addendum already went in and I just needed to rebase. Apologies for the noise.

> IndexTool should be able to rebuild tenant-owned indexes
> --------------------------------------------------------
>
>                 Key: PHOENIX-4940
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4940
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.14.0, 5.0.0
>            Reporter: Geoffrey Jacoby
>            Assignee: Gokcen Iskender
>            Priority: Major
>             Fix For: 4.15.0, 5.1
>
>         Attachments: PHOENIX-4940-4.x.patch, PHOENIX-4940-addendum.patch
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> IndexTool uses global connections to lookup the indexes which it's asked to rebuild, 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 rebuilding those indexes as well. 



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