Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A61FB200C21 for ; Mon, 20 Feb 2017 12:14:18 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A4B12160B62; Mon, 20 Feb 2017 11:14:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EE5AB160B73 for ; Mon, 20 Feb 2017 12:14:17 +0100 (CET) Received: (qmail 11419 invoked by uid 500); 20 Feb 2017 11:14:17 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 11410 invoked by uid 99); 20 Feb 2017 11:14:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2017 11:14:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C7A12C0258 for ; Mon, 20 Feb 2017 11:14:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 9AipPf1BiuBC for ; Mon, 20 Feb 2017 11:14:16 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 78B125F1B8 for ; Mon, 20 Feb 2017 11:14:15 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 785D7E073C for ; Mon, 20 Feb 2017 11:13:44 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 36C7124121 for ; Mon, 20 Feb 2017 11:13:44 +0000 (UTC) Date: Mon, 20 Feb 2017 11:13:44 +0000 (UTC) From: "Padma Priya Nagaraj (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20079) Unable to filter by job id MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 20 Feb 2017 11:14:18 -0000 [ 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)