[
https://issues.apache.org/jira/browse/HIVE-26415?focusedWorklogId=798299&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-798299
]
ASF GitHub Bot logged work on HIVE-26415:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Aug/22 07:25
Start Date: 05/Aug/22 07:25
Worklog Time Spent: 10m
Work Description: pudidic commented on PR #3467:
URL: https://github.com/apache/hive/pull/3467#issuecomment-1206132821
+1. Looks good to me.
By the way, I need a write access as a committer. It's been 4 years. I'm new
to Apache Hive on GitHub.
Issue Time Tracking
-------------------
Worklog Id: (was: 798299)
Remaining Estimate: 167h (was: 167h 10m)
Time Spent: 1h (was: 50m)
> 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: 1h
> Remaining Estimate: 167h
>
> 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)
