[jira] [Commented] (AMBARI-14081) HiveView fails to find DAGs corresponding to query

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-14081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028438#comment-15028438 ] 

Hadoop QA commented on AMBARI-14081:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12774473/AMBARI-14081_branch-2.1.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4403//console

This message is automatically generated.

> 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
>
>         Attachments: AMBARI-14081_branch-2.1.patch
>
>
> 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)