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/27 21:14:00 UTC
[jira] [Updated] (PHOENIX-5168) IndexScrutinyTool cannot output to
table when analyzing tenant-owned indexes
[ https://issues.apache.org/jira/browse/PHOENIX-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gokcen Iskender updated PHOENIX-5168:
-------------------------------------
Description:
IndexScrutiny has a new feature of using tenant connections (when tenant-Id parameter is used) to lookup the indexes on tenant views.
When tenant-id option is provided and output-format is set to TABLE, we get an error that PHOENIX_SCRUTINY_TABLE cannot be created due to permission.
We should be able to output to a table when tenant-id option is used.
Note that output-format set to FILE is supported.
was:
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.
> IndexScrutinyTool cannot output to table when analyzing tenant-owned indexes
> ----------------------------------------------------------------------------
>
> Key: PHOENIX-5168
> URL: https://issues.apache.org/jira/browse/PHOENIX-5168
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Gokcen Iskender
> Assignee: Gokcen Iskender
> Priority: Major
>
> IndexScrutiny has a new feature of using tenant connections (when tenant-Id parameter is used) to lookup the indexes on tenant views.
> When tenant-id option is provided and output-format is set to TABLE, we get an error that PHOENIX_SCRUTINY_TABLE cannot be created due to permission.
> We should be able to output to a table when tenant-id option is used.
> Note that output-format set to FILE is supported.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)