You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2022/10/21 07:21:01 UTC
[jira] [Updated] (HIVE-25925) Improve the oldest_ready_for_cleaning_age_in_sec compaction metric
[ https://issues.apache.org/jira/browse/HIVE-25925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stamatis Zampetakis updated HIVE-25925:
---------------------------------------
Fix Version/s: (was: 4.0.0)
I cleared the fixVersion field since this ticket is still open. Please review this ticket and if the fix is already committed to a specific version please set the version accordingly and mark the ticket as RESOLVED.
According to the [JIRA guidelines|https://cwiki.apache.org/confluence/display/Hive/HowToContribute] the fixVersion should be set only when the issue is resolved/closed.
> Improve the oldest_ready_for_cleaning_age_in_sec compaction metric
> ------------------------------------------------------------------
>
> Key: HIVE-25925
> URL: https://issues.apache.org/jira/browse/HIVE-25925
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 4.0.0
> Reporter: Viktor Csomor
> Assignee: Viktor Csomor
> Priority: Minor
> Labels: pull-request-available
>
> Instead of calculating the age on the Database side for the {{oldest_ready_for_cleaning_age_in_sec}} we can calculate it in the AcidMetricsService. At the moment the {{CQ_COMMIT_TIME}} is not exposed in the {{ShowCompactResponse}} therefore the calculation happens in the db query.
> It has to be assessed whether it worth to expose this field or not?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)