You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@hive.apache.org by GitBox <gi...@apache.org> on 2021/02/25 07:55:24 UTC

[GitHub] [hive] pvargacl edited a comment on pull request #2017: HIVE-24753: Non blocking DROP PARTITION implementation

pvargacl edited a comment 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 ...
   - there will be a race condition in the cleaner and the create partition I think, what happens if Cleaner starts to run, checks if the partition was dropped, so decides it has to delete the partition directory, but now a create partition comes and a new query starts to write a new delta. This should be handled. 


----------------------------------------------------------------
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: gitbox-unsubscribe@hive.apache.org
For additional commands, e-mail: gitbox-help@hive.apache.org