[
https://issues.apache.org/jira/browse/PHOENIX-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Poon updated PHOENIX-4907:
----------------------------------
Fix Version/s: 4.14.1
> IndexScrutinyTool should use empty catalog instead of null
> ----------------------------------------------------------
>
> Key: PHOENIX-4907
> URL: https://issues.apache.org/jira/browse/PHOENIX-4907
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
> Fix For: 4.15.0, 4.14.1, 5.1.0
>
> Attachments: PHOENIX-4907.patch
>
>
> Before executing, the index scrutiny tool does a sanity check to make sure
> that the given data table and index are valid and related to each other. This
> check uses the JDBC metadata API, and passes in null for the catalog name.
> Unfortunately, a null entry for catalog causes Phoenix to omit tenant_id from
> the query against System.Catalog, causing a table scan, which can be lengthy
> or time out if the server has too many views.
> It should pass in the empty string for catalog, which will make Phoenix
> filter on "WHERE tenant_id is NULL", which will avoid the table scan.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
