[
https://issues.apache.org/jira/browse/HIVE-11495?focusedWorklogId=815501&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-815501
]
ASF GitHub Bot logged work on HIVE-11495:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Oct/22 07:47
Start Date: 11/Oct/22 07:47
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on PR #3656:
URL: https://github.com/apache/hive/pull/3656#issuecomment-1274240038
@simhadri-g I don't think it's a good idea to populate something in TXNS
table for further troubleshooting. Once a transaction is aborted and there is
nothing to clean up, the corresponding row in TXNS table would be immediately
deleted.
Note: aborted txns prevent the cleanup of ACID metadata, so we try to keep
their life short.
I think we should try to focus on improving the logging here. However, if
you want to persist abort reason in DB, maybe we need to pass the aborted txn
reason through the compaction tables as well. Those could be used later on for
the inspection.
Issue Time Tracking
-------------------
Worklog Id: (was: 815501)
Time Spent: 0.5h (was: 20m)
> 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: Simhadri Govindappa
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Should add TXNS.COMMENT field or something like that so that if the system
> aborts a transaction (due to timeout, for example) we can add a message to
> that effect to the aborted 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)
