[
https://issues.apache.org/jira/browse/HIVE-26415?focusedWorklogId=797516&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-797516
]
ASF GitHub Bot logged work on HIVE-26415:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Aug/22 06:44
Start Date: 03/Aug/22 06:44
Worklog Time Spent: 10m
Work Description: pudidic commented on code in PR #3467:
URL: https://github.com/apache/hive/pull/3467#discussion_r936292595
##########
metastore/scripts/upgrade/hive/hive-schema-4.0.0-alpha-2.hive.sql:
##########
@@ -1980,7 +1980,8 @@ SELECT
FROM_UNIXTIME(END_TIME) as END_TIME,
END_TIME-START_TIME as ELAPSED,
ERROR_MESSAGE,
- FROM_UNIXTIME(LAST_UPDATE_TIME) AS LAST_UPDATE_TIME
+ FROM_UNIXTIME(LAST_UPDATE_TIME) AS LAST_UPDATE_TIME,
+ START_TIME as START_TIME_SINCE_EPOCH
FROM
Review Comment:
There is upgrade-4.0.0-alpha1-to-4.0.0-alpha-2.hive.sql, too.
Issue Time Tracking
-------------------
Worklog Id: (was: 797516)
Remaining Estimate: 167h 20m (was: 167.5h)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> Remaining Estimate: 167h 20m
>
> 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)
