[jira] [Updated] (HIVE-20516) alter table drop partition should be compatible with old metastore, as partition pruner does

["Stamatis Zampetakis (Jira)" <ji...@apache.org>]

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

Stamatis Zampetakis updated HIVE-20516:
---------------------------------------
    Fix Version/s:     (was: 3.1.0)

I cleared the fixVersion field since this ticket is not resolved. Please review this ticket and if the fix is already committed to a specific version please set the version accordingly and mark the ticket as RESOLVED.

According to the JIRA guidelines (https://cwiki.apache.org/confluence/display/Hive/HowToContribute) the fixVersion should be set only when the issue is resolved/closed.

> alter table drop partition should be compatible with old metastore, as partition pruner does
> --------------------------------------------------------------------------------------------
>
>                 Key: HIVE-20516
>                 URL: https://issues.apache.org/jira/browse/HIVE-20516
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 3.0.0
>         Environment: all
>            Reporter: jinzheng
>            Assignee: jinzheng
>            Priority: Major
>         Attachments: temp.diff
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
>     After the change of  HIVE-4914, we always push the partition expression to metastore, to avoid filtering partition by partition names.
>     And HIVE-4914 added some protection in Partition pruner, in case that metastore may not have api of get_partitions_by_expr.
>     Therefore, we should also add similar protection to another calling point, when dealing with "alter table drop partition".



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