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

Posted to issues@hive.apache.org by "Zhihua Deng (Jira)" <ji...@apache.org> on 2024/08/16 09:02:00 UTC

[jira] [Updated] (HIVE-28447) Remove the filtering around the tableExists

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

Zhihua Deng updated HIVE-28447:
-------------------------------
    Description: The tableExists in HiveMetaStoreClient is to check whether a table exists, in current implementation an authorization filtering is performed on both the client and server side, this API would return false even though there is such a table in HMS due to this filter, which is against the role of this method. As this method doesn't breach any internal details of the table, so it would be better to remove the filtering, and make it accept the pattern based tableName or databaseName.  (was: The tableExists in HiveMetaStoreClient is to check whether a table exists, in current implementation an authorization filtering is performed on both the client and server side, this API would return false even though there is such an table in HMS due to this filter, which is against the role of this method. As this method doesn't breach any internal details of the table, so it would be better to remove the filtering, and make it accept the pattern based tableName or databaseName.)

> Remove the filtering around the tableExists
> -------------------------------------------
>
>                 Key: HIVE-28447
>                 URL: https://issues.apache.org/jira/browse/HIVE-28447
>             Project: Hive
>          Issue Type: Improvement
>          Components: Standalone Metastore
>            Reporter: Zhihua Deng
>            Priority: Major
>
> The tableExists in HiveMetaStoreClient is to check whether a table exists, in current implementation an authorization filtering is performed on both the client and server side, this API would return false even though there is such a table in HMS due to this filter, which is against the role of this method. As this method doesn't breach any internal details of the table, so it would be better to remove the filtering, and make it accept the pattern based tableName or databaseName.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)