[
https://issues.apache.org/jira/browse/HIVE-24432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242511#comment-17242511
]
David Mollitor commented on HIVE-24432:
---------------------------------------
[~anishek] Yes. I thought about implementing it this way, however, it's not
always that simple. Since Hive is using an ORM it can sometimes have a
negative effect when doing modifications to the DB directly since the ORM
caches fall out of sync with the state of the DB after that modification. I
think in this case, it might be OK, but less risk do it in this manner and the
clean up isn't too important in terms of performance.
> Delete Notification Events in Batches
> -------------------------------------
>
> Key: HIVE-24432
> URL: https://issues.apache.org/jira/browse/HIVE-24432
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 3.2.0
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Notification events are loaded in batches (reduces memory pressure on the
> HMS), but all of the deletes happen under a single transactions and, when
> deleting many records, can put a lot of pressure on the backend database.
> Instead, delete events in batches (in different transactions) as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
