Description
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.
Attachments
Attachments
Issue Links
- is cloned by
-
PHOENIX-5168 IndexScrutinyTool cannot output to table when analyzing tenant-owned indexes
- Closed
- relates to
-
PHOENIX-5456 IndexScrutinyTool slow for indexes on multitenant tables
- Closed
- links to