[
https://issues.apache.org/jira/browse/HIVE-23619?focusedWorklogId=448528&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-448528
]
ASF GitHub Bot logged work on HIVE-23619:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Jun/20 15:04
Start Date: 19/Jun/20 15:04
Worklog Time Spent: 10m
Work Description: kgyrtkirk commented on pull request #1146:
URL: https://github.com/apache/hive/pull/1146#issuecomment-646686235
I wasn't pursuing a test because I suspected it will need some interesting
"tweaks"
It's awesome that you've wrote a test for this! :)
I'm wondering about renaming it from `reexecutelostam` to something shorter
- or more easily readable ;
it's hard to read correctly at first glance:
shorter maybe: `amlost` or we may use underscore in some way as well
`lost_am`, `reexecute_lost_am` ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 448528)
Time Spent: 40m (was: 0.5h)
> HiveServer2 should retry query if the TezAM running it gets killed
> ------------------------------------------------------------------
>
> Key: HIVE-23619
> URL: https://issues.apache.org/jira/browse/HIVE-23619
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Reporter: Adesh Kumar Rao
> Assignee: Adesh Kumar Rao
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> If the TezAM was running a query and it gets killed because of external
> factors like node going node, HS2 should retry the query in different TezAM.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
