[
https://issues.apache.org/jira/browse/AMBARI-19062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15714739#comment-15714739
]
Nitiraj Singh Rathore commented on AMBARI-19062:
------------------------------------------------
In Hive 1.5.0, the execution of the job has been moved to background threads
and hence if the user goes away(closes) from the browser, the job still
continues to run in the backend and will finish with a valid terminal
state(either FAILED or SUCCESS). Previously this was not the case because all
query to HS2 used to stop when the user closed the browser and hence to get the
final terminal state we had to query ATS so that we could update the results in
Hive browser database. The update used to happen when the user clicked on the
history tab. So, for every job we used to query ATS for getting the terminal
state. In the process it also used to bring in the information for the queries
that were not run from the hive browser(may be from beeline or hive cli).
So, to fix this issue we are going to stop the call for ATS when the user
clicks on the history tab. Because as execution has moved to background
threads, the state of the job in the database is going to be always correct and
we will consider that to be the source of truth.
The thing that we will miss out are the display of the jobs that are not run
from hive browser, but to meet the SLA for the history tab and till the time
ATS does not provide a bulk API to fetch the information we will have to miss
that feature.
> Hive view history tab does not list queries, if there are large number of
> queries
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-19062
> URL: https://issues.apache.org/jira/browse/AMBARI-19062
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.4.0
> Reporter: Nitiraj Singh Rathore
> Assignee: Nitiraj Singh Rathore
> Fix For: 2.5.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
