Transactions that got timed out are not getting logged as 'ABORTED' in NOTIFICATION_LOG

Scenario:

Let's there are 100 transactions opened. These 100 will be logged in notification_log and when replicated, they will get created in target cluster. 

Now 50 out of these 100 transactions got aborted due to timeout and got removed from HMS. In this step, we are not logging those transactions in to notification_log. 

So next time when we do replication, these 50 aborted transactions will not be replicated.

As a result in the target cluster the transactions that got created earlier will only get removed after number of days configured in config 

hive.repl.txn.timeout (11 days default)

Actually, we have the logic to log aborted transactions if they got aborted for some other reason but not for those that are getting timed out.