[
https://issues.apache.org/jira/browse/HIVE-26415?focusedWorklogId=801852&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-801852
]
ASF GitHub Bot logged work on HIVE-26415:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Aug/22 03:16
Start Date: 19/Aug/22 03:16
Worklog Time Spent: 10m
Work Description: pudidic commented on PR #3467:
URL: https://github.com/apache/hive/pull/3467#issuecomment-1220197644
I tested the failing TestJdbcWithMiniHS2#testHttpRetryOnServerIdleTimeout on
my laptop. It passed. As it's a trivial change, I'll merge it.
Issue Time Tracking
-------------------
Worklog Id: (was: 801852)
Remaining Estimate: 166h 50m (was: 167h)
Time Spent: 1h 10m (was: 1h)
> 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 10m
> Remaining Estimate: 166h 50m
>
> 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)
