[
https://issues.apache.org/jira/browse/HIVE-24753?focusedWorklogId=557771&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-557771
]
ASF GitHub Bot logged work on HIVE-24753:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Feb/21 07:43
Start Date: 25/Feb/21 07:43
Worklog Time Spent: 10m
Work Description: pvargacl commented on pull request #2017:
URL: https://github.com/apache/hive/pull/2017#issuecomment-785691173
I missing some features, should these part of this PR?
- shouldn't the lock type changed from exclusive to excl_write if we use
this kind of drop?
- shouldn't he Cleaner later delete the whole partition directory if it was
not recreated?
- I think you should add many test, around drop and recreate, what happens
if you recreate in different scenarios (while there is an old read still
running, when you overlap with the cleaner, when it was already cleaned up ...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 557771)
Time Spent: 1h (was: 50m)
> Non blocking DROP PARTITION implementation
> ------------------------------------------
>
> Key: HIVE-24753
> URL: https://issues.apache.org/jira/browse/HIVE-24753
> Project: Hive
> Issue Type: New Feature
> Reporter: Zoltan Chovan
> Assignee: Zoltan Chovan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Implement a way to execute drop partition operations in a way that doesn't
> have to wait for currently running read operations to be finished.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
