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 C601D2009D9 for ; Thu, 19 May 2016 23:38:16 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C480A160A00; Thu, 19 May 2016 21:38:16 +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 16E671609AE for ; Thu, 19 May 2016 23:38:15 +0200 (CEST) Received: (qmail 85796 invoked by uid 500); 19 May 2016 21:38:15 -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 85785 invoked by uid 99); 19 May 2016 21:38:15 -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; Thu, 19 May 2016 21:38:15 +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 BB3E3C006B for ; Thu, 19 May 2016 21:38:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.221 X-Spam-Level: X-Spam-Status: No, score=-3.221 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id N5SqFACjenJo for ; Thu, 19 May 2016 21:38:14 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with SMTP id 942AA5F1F3 for ; Thu, 19 May 2016 21:38:13 +0000 (UTC) Received: (qmail 85640 invoked by uid 99); 19 May 2016 21:38:12 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2016 21:38:12 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C96C12C1F58 for ; Thu, 19 May 2016 21:38:12 +0000 (UTC) Date: Thu, 19 May 2016 21:38:12 +0000 (UTC) From: "Balu Vellanki (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FALCON-1974) Cluster update : Allow superuser to update bundle/coord of dependent entities MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 19 May 2016 21:38:17 -0000 [ https://issues.apache.org/jira/browse/FALCON-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balu Vellanki updated FALCON-1974: ---------------------------------- Description: When an entity is updated, the bundle/coordinator of dependent feed and process entities should be updated in the workflow engine. These feeds and processes can be scheduled in workflow engine by different users. The superuser submitting the update request may not have permissions to update the bundle/coord of dependent entities. So the OozieWorkflowEngine should allow superuser to switch to bundle.getUser() and update the bundle/coord. Once the update is complete, OozieWorkflowEngine should switch back to superUser. The above fix would also require Falcon to confirm that the request to update dependent entities can be submitted only by superuser. was:When an entity is updated, the bundle/coordinator of dependent feed and process entities should be updated in the workflow engine. The superuser submitting the update request may not have permissions to update the bundle/coord of dependent entities. So the OozieWorkflowEngine should allow superuser to switch to bundle.getUser() and update the bundle/coord. Once the update is complete, OozieWorkflowEngine should switch back to superUser. > Cluster update : Allow superuser to update bundle/coord of dependent entities > ----------------------------------------------------------------------------- > > Key: FALCON-1974 > URL: https://issues.apache.org/jira/browse/FALCON-1974 > Project: Falcon > Issue Type: Bug > Reporter: Balu Vellanki > Assignee: Balu Vellanki > Fix For: 0.10 > > > When an entity is updated, the bundle/coordinator of dependent feed and process entities should be updated in the workflow engine. These feeds and processes can be scheduled in workflow engine by different users. > The superuser submitting the update request may not have permissions to update the bundle/coord of dependent entities. So the OozieWorkflowEngine should allow superuser to switch to bundle.getUser() and update the bundle/coord. Once the update is complete, OozieWorkflowEngine should switch back to superUser. > The above fix would also require Falcon to confirm that the request to update dependent entities can be submitted only by superuser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)