[
https://issues.apache.org/jira/browse/HIVE-26280?focusedWorklogId=780329&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-780329
]
ASF GitHub Bot logged work on HIVE-26280:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Jun/22 14:49
Start Date: 10/Jun/22 14:49
Worklog Time Spent: 10m
Work Description: klcopp commented on code in PR #3340:
URL: https://github.com/apache/hive/pull/3340#discussion_r894614373
##########
metastore/scripts/upgrade/hive/hive-schema-4.0.0-alpha-2.hive.sql:
##########
@@ -1138,6 +1144,9 @@ CREATE EXTERNAL TABLE IF NOT EXISTS
`COMPLETED_COMPACTIONS` (
`CC_HIGHEST_WRITE_ID` bigint,
`CC_HADOOP_JOB_ID` string,
`CC_ERROR_MESSAGE` string,
+ `CC_NEXT_TXN_ID` bigint,
Review Comment:
Well, just thinking about troubleshooting situations... txnIds will be
present in the logs and might be still left open in the TXNS table. NEXT_TXN_ID
will tell you when the cleaner should have picked up the compaction for
cleaning.
Do you think there's any downside to propagating them?
Issue Time Tracking
-------------------
Worklog Id: (was: 780329)
Time Spent: 1h (was: 50m)
> Copy more data into COMPLETED_COMPACTIONS for better supportability
> -------------------------------------------------------------------
>
> Key: HIVE-26280
> URL: https://issues.apache.org/jira/browse/HIVE-26280
> Project: Hive
> Issue Type: Improvement
> Components: Transactions
> Reporter: Karen Coppage
> Assignee: Karen Coppage
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> There is some information in COMPACTION_QUEUE that doesn't get copied over to
> COMPLETED_COMPACTIONS when compaction completes. It would help with
> supportability if COMPLETED_COMPACTIONS (and especially the view of it in the
> SYS database) also contained this information.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
