You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/11/18 05:19:00 UTC
[jira] [Work logged] (HIVE-26415) Add epoch time in the information_schema.scheduled_executions view
[ https://issues.apache.org/jira/browse/HIVE-26415?focusedWorklogId=827043&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-827043 ]
ASF GitHub Bot logged work on HIVE-26415:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Nov/22 05:18
Start Date: 18/Nov/22 05:18
Worklog Time Spent: 10m
Work Description: pudidic commented on PR #3467:
URL: https://github.com/apache/hive/pull/3467#issuecomment-1319559490
LGTM +1. I'll merge it.
Issue Time Tracking
-------------------
Worklog Id: (was: 827043)
Remaining Estimate: 166.5h (was: 166h 40m)
Time Spent: 1.5h (was: 1h 20m)
> Add epoch time in the information_schema.scheduled_executions view
> ------------------------------------------------------------------
>
> Key: HIVE-26415
> URL: https://issues.apache.org/jira/browse/HIVE-26415
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 4.0.0
> Reporter: Imran
> Assignee: Shreenidhi
> Priority: Major
> Labels: pull-request-available
> Original Estimate: 168h
> Time Spent: 1.5h
> Remaining Estimate: 166.5h
>
> information_schema.scheduled_executions shows time as the System time. replication_metrics shows time in epoch time.
> Only way to corelate the two is using the scheduled_execution id. Looking at the time at the 2 tables causes some confusion. So we can add a new column in the information_schema.scheduled_executions view displaying the epoch time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)