phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <>
Subject [jira] [Created] (PHOENIX-4907) IndexScrutinyTool should use empty catalog instead of null
Date Mon, 17 Sep 2018 22:45:00 GMT
Geoffrey Jacoby created PHOENIX-4907:

             Summary: IndexScrutinyTool should use empty catalog instead of null
                 Key: PHOENIX-4907
             Project: Phoenix
          Issue Type: Improvement
    Affects Versions: 5.0.0, 4.15.0
            Reporter: Geoffrey Jacoby
            Assignee: Geoffrey Jacoby

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

View raw message