You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2018/03/15 01:41:00 UTC

[jira] [Updated] (PHOENIX-4654) In PhoenixDatabaseMetaData.addTenantIdFilter add WHERE TENANT_ID is NULL when the connection used does not have a tenant id

     [ https://issues.apache.org/jira/browse/PHOENIX-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas D'Silva updated PHOENIX-4654:
------------------------------------
    Description: or else we end up doing a full table scan  (was: We are currently doing a full table scan since we do not include a tenant id filter in PhoenixDatabaseMetaData.getTables())
        Summary: In PhoenixDatabaseMetaData.addTenantIdFilter add WHERE TENANT_ID is NULL when the connection used does not have a tenant id   (was: In PhoenixDatabaseMetaData.getTables add the connection's tenant id to where clause filter)

> In PhoenixDatabaseMetaData.addTenantIdFilter add WHERE TENANT_ID is NULL when the connection used does not have a tenant id 
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4654
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4654
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Thomas D'Silva
>            Assignee: Thomas D'Silva
>            Priority: Major
>
> or else we end up doing a full table scan



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)