You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "David Lavati (Jira)" <ji...@apache.org> on 2022/11/22 10:47:00 UTC

[jira] [Updated] (HIVE-22585) Clean up catalog/db/table name usage

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

David Lavati updated HIVE-22585:
--------------------------------
    Status: Open  (was: Patch Available)

> Clean up catalog/db/table name usage
> ------------------------------------
>
>                 Key: HIVE-22585
>                 URL: https://issues.apache.org/jira/browse/HIVE-22585
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: David Lavati
>            Assignee: David Lavati
>            Priority: Major
>              Labels: pull-request-available, refactor
>         Attachments: HIVE-22585.01.patch, HIVE-22585.02.patch, HIVE-22585.03.patch, HIVE-22585.04.patch, HIVE-22585.05.patch
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> This is a followup to HIVE-21198 to address some additional improvement ideas for the TableName object mentioned inĀ [https://github.com/apache/hive/pull/550] and attempt to remove all the fishy usages of db/tablenames, as a number of places still rely on certain state changes/black magic.
> This change includes the following:
> * Remove reliance on Utilities.getDbTableName
> * Introduce a contract in TableName to always store catalog.dbname.tablename in lowercase
> * Make TableName a parsable type for ExplainTask
> * Additional refactors to leverage the TableName object



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