[
https://issues.apache.org/jira/browse/PHOENIX-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780195#comment-16780195
]
Hudson commented on PHOENIX-5089:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.4 #81 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.4/81/])
PHOENIX-5089 Add tenantId parameter to IndexScrunityTool (gjacoby: rev
cc9754fff840f38d13c3adb0c963296959fff3fa)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexScrutinyTool.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexScrutinyToolIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/util/IndexColumnNames.java
> 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
>
> Attachments: PHOENIX-5089-4x-1.4.patch, PHOENIX-5089.patch
>
> Time Spent: 2.5h
> 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)
