ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Padma Priya Nagaraj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20079) Unable to filter by job id
Date Mon, 20 Feb 2017 11:13:44 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Padma Priya Nagaraj updated AMBARI-20079:
-----------------------------------------
    Attachment: Screen Shot 2017-02-16.png

> Unable to filter by job id
> --------------------------
>
>                 Key: AMBARI-20079
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20079
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.5.0
>            Reporter: Padma Priya Nagaraj
>            Assignee: Padma Priya Nagaraj
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: Screen Shot 2017-02-16.png
>
>
> After attempting to resume a random SUSPENDED existing workflow 0000078-170215133231623-oozie-oozi-W
(ran by the nightly system tests via hrt_qa user), the workflow went into RUNNING state. I
wanted to see that workflow by itself on the dashboard, so I used filter criteria with the
following syntax:
> jobid=0000078-170215133231623-oozie-oozi-W
> jobid:0000078-170215133231623-oozie-oozi-W
> The first one returned:
> Remote api failed
> The second one showed the same error message but also a perptual animated busy loading
icon.
> I expected that if my syntax was incorrect, it would say so like "jobid:..." is not correct,
do you mean "Job Id=" or something to that effect. Also, for the second case, there should
be a fast fail, rather than a perpetual hanging.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message