You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "DIPAYAN BHOWMICK (JIRA)" <ji...@apache.org> on 2015/11/26 07:22:10 UTC
[jira] [Created] (AMBARI-14081) HiveView fails to find DAGs
corresponding to query
DIPAYAN BHOWMICK created AMBARI-14081:
-----------------------------------------
Summary: HiveView fails to find DAGs corresponding to query
Key: AMBARI-14081
URL: https://issues.apache.org/jira/browse/AMBARI-14081
Project: Ambari
Issue Type: Bug
Components: ambari-views
Reporter: DIPAYAN BHOWMICK
Assignee: DIPAYAN BHOWMICK
Fix For: 2.1.3
In ATS 1.5, The DAG name is no longer set to the query id. It's set to a descriptive term or user chosen name. The Query ID is stored in the caller context, which is also indexed. A a version field to the hive query ATS log entry. If the version is >= 2 the new caller context has to be used for search. If the version field doesn't exist the old way of searching for DAGs applies.
So, Hive view should query callerId if the version id >=2 else it should fall back to query by dagName(backward compatibility for older ATS).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)