[ https://issues.apache.org/jira/browse/HIVE-11495?focusedWorklogId=836884&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-836884 ]
ASF GitHub Bot logged work on HIVE-11495: ----------------------------------------- Author: ASF GitHub Bot Created on: 04/Jan/23 12:38 Start Date: 04/Jan/23 12:38 Worklog Time Spent: 10m Work Description: veghlaci05 commented on PR #3908: URL: https://github.com/apache/hive/pull/3908#issuecomment-1370877808 > @veghlaci05 Based on a earlier conversation for the same ticket - [#3656 (comment)](https://github.com/apache/hive/pull/3656#issuecomment-1274240038) It was decided that we must opt for logging instead of persisting it. I have edited the same in the Jira as well. In this please ignore my comments regarding the presistence. While I still think persisting would be better, I have to admit it would make this task significantly more complicated. (As @deniskuzZ pointed out, aborted TXNs are cleaned up quickly). Issue Time Tracking ------------------- Worklog Id: (was: 836884) Time Spent: 4h (was: 3h 50m) > Add aborted reason to transaction information. > ---------------------------------------------- > > Key: HIVE-11495 > URL: https://issues.apache.org/jira/browse/HIVE-11495 > Project: Hive > Issue Type: Improvement > Components: Metastore, Transactions > Affects Versions: 1.0.0 > Reporter: Eugene Koifman > Assignee: Sourabh Badhya > Priority: Major > Labels: pull-request-available > Time Spent: 4h > Remaining Estimate: 0h > > Add logging messages mentioning the reason to abort the transaction. > Another reason: Commit can fail due to a conflicting write from another txn > (since HIVE-13395) -- This message was sent by Atlassian Jira (v8.20.10#820010)