[
https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875831#comment-15875831
]
Hudson commented on AMBARI-20079:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1041 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1041/])
AMBARI-20079. Unable to filter by job id.(Padma Priya N via gauravn7) (grvngr:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fa13f66c8bc393b9b3fd6e84f31ffa2deaa379fa])
* (edit)
contrib/views/wfmanager/src/main/resources/ui/app/components/search-create-new-bar.js
> 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
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20079_trunk.patch, 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)
