Failure in direct SQL processing do not undo the changes made to database before fallback to JDO resulting in stale entries in database forever

[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 deleted in the same transaction during direct SQL processing.

[Steps to reproduce] 

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