You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Venugopal Reddy K (Jira)" <ji...@apache.org> on 2023/01/23 09:57:00 UTC

[jira] [Created] (HIVE-26976) Failure in direct SQL processing do not undo the changes made to database before fallback to JDO resulting in stale entries in database forever

Venugopal Reddy K created HIVE-26976:
----------------------------------------

             Summary: Failure in direct SQL processing do not undo the changes made to database before fallback to JDO resulting in stale entries in database forever
                 Key: HIVE-26976
                 URL: https://issues.apache.org/jira/browse/HIVE-26976
             Project: Hive
          Issue Type: Bug
          Components: Metastore
            Reporter: Venugopal Reddy K
         Attachments: image-2023-01-23-15-23-00-975.png

*[Description]* 

Failure in direct SQL processing do not undo the changes made to database before falling back to JDO based processing. Thus results in stale/dangling entries in database forever.

For instance, during dropPartitions() direct SQL processing, after dropping rows from few tables(like PARTITIONS, PARTITION_PARAMS, PARTITION_KEY_VALS etc), it causes typecast exception in dropStorageDescriptors() and fallback to JDO processing. But datanucleus JDO processing cannot delete rows from remaining tables(i.e., from sds, serdes, sds_params, serde_params, sort_cols, bucketing_cols, skewed cols/values/location if any for the partitions) since the partition is already in the same transaction during direct SQL processing.

!image-2023-01-23-15-23-00-975.png!

 

 

*[Steps to reproduce]* 

Reproduction steps are described in issue - [https://issues.apache.org/jira/browse/HIVE-26860|https://issues.apache.org/jira/browse/HIVE-26860]



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