Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1EBF018942 for ; Wed, 6 Jan 2016 03:41:47 +0000 (UTC) Received: (qmail 2147 invoked by uid 500); 6 Jan 2016 03:41:42 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 2099 invoked by uid 500); 6 Jan 2016 03:41:41 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 2072 invoked by uid 99); 6 Jan 2016 03:41:41 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jan 2016 03:41:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EEA90C0034 for ; Wed, 6 Jan 2016 03:41:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.979 X-Spam-Level: X-Spam-Status: No, score=0.979 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id K8Wsceoyzf9o for ; Wed, 6 Jan 2016 03:41:40 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 5ED8823192 for ; Wed, 6 Jan 2016 03:41:40 +0000 (UTC) Received: (qmail 1742 invoked by uid 99); 6 Jan 2016 03:41:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jan 2016 03:41:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E80482C1F64 for ; Wed, 6 Jan 2016 03:41:39 +0000 (UTC) Date: Wed, 6 Jan 2016 03:41:39 +0000 (UTC) From: "Ajay Yadava (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Issue Comment Deleted] (FALCON-1720) Rerun API does not rerun succeeded instances MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FALCON-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-1720: -------------------------------- Comment: was deleted (was: [~pavan kumar] If user specifies properties then why should the force option be ignored. In most cases I think they will want to do force option along with props.) > Rerun API does not rerun succeeded instances > -------------------------------------------- > > Key: FALCON-1720 > URL: https://issues.apache.org/jira/browse/FALCON-1720 > Project: Falcon > Issue Type: Bug > Components: scheduler > Affects Versions: 0.9 > Reporter: Pragya Mittal > Assignee: pavan kumar kolamuri > Attachments: FALCON-1720-v1.patch, FALCON-1720.patch > > > When entity is scheduled via native scheduler, rerun api does not force rerun the succeeded instances. Although oozie run count gets incremented but state of instance does not change from 'SUCCEEDED' to 'RUNNING' -- This message was sent by Atlassian JIRA (v6.3.4#6332)