[jira] [Updated] (HIVE-10421) DROP TABLE with qualified table name ignores database name when checking partitions

["Jason Dere (JIRA)" <ji...@apache.org>]

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

Jason Dere updated HIVE-10421:
------------------------------
    Attachment: HIVE-10421.1.patch

> DROP TABLE with qualified table name ignores database name when checking partitions
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-10421
>                 URL: https://issues.apache.org/jira/browse/HIVE-10421
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>         Attachments: HIVE-10421.1.patch
>
>
> Hive was only recently changed to allow "drop table dbname.tabname". However DDLTask.dropTable() is still using an older version of Hive.getPartitionNames(), which only took in a single string for the table name, rather than the database and table names. As a result Hive is filling in the current database name as the dbname during the listPartitions call to the MetaStore.
> It also appears that on the Hive Metastore side, in the non-auth path there is no validation to check that the dbname.tablename actually exists - this call simply returns back an empty list of partitions, which causes the table to be dropped without checking any of the partition information. I will open a separate issue for this one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)