Return-Path: 
 <commits-return-4021-apmail-helix-commits-archive=helix.apache.org@helix.apache.org>
X-Original-To: apmail-helix-commits-archive@minotaur.apache.org
Delivered-To: apmail-helix-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 196A610743
	for <apmail-helix-commits-archive@minotaur.apache.org>;
 Wed, 12 Mar 2014 03:33:09 +0000 (UTC)
Received: (qmail 68997 invoked by uid 500); 12 Mar 2014 03:33:08 -0000
Delivered-To: apmail-helix-commits-archive@helix.apache.org
Received: (qmail 68975 invoked by uid 500); 12 Mar 2014 03:33:06 -0000
Mailing-List: contact commits-help@helix.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@helix.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@helix.apache.org>
List-Post: <mailto:commits@helix.apache.org>
List-Id: <commits.helix.apache.org>
Reply-To: dev@helix.apache.org
Delivered-To: mailing list commits@helix.apache.org
Received: (qmail 68957 invoked by uid 99); 12 Mar 2014 03:33:05 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Mar 2014 03:33:05 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with SMTP; Wed, 12 Mar 2014 03:33:04 +0000
Received: (qmail 68088 invoked by uid 99); 12 Mar 2014 03:32:44 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Mar 2014 03:32:44 +0000
Date: Wed, 12 Mar 2014 03:32:44 +0000 (UTC)
From: "Shi Lu (JIRA)" <jira@apache.org>
To: commits@helix.incubator.apache.org
Message-ID: <JIRA.12689605.1390006945741.49024.1394595164213@arcas>
In-Reply-To: <JIRA.12689605.1390006945741@arcas>
References: <JIRA.12689605.1390006945741@arcas>
Subject: [jira] [Commented] (HELIX-359) For FULL_AUTO, evaluate the order
 disabling can happen at each scope
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/HELIX-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931353#comment-13931353 ] 

Shi Lu commented on HELIX-359:
------------------------------

There are use cases that 2 different resources can contain same set of partition names. Thus we need to support disable <partitionSet> within <resource> across the whole cluster.

> For FULL_AUTO, evaluate the order disabling can happen at each scope
> --------------------------------------------------------------------
>
>                 Key: HELIX-359
>                 URL: https://issues.apache.org/jira/browse/HELIX-359
>             Project: Apache Helix
>          Issue Type: Task
>            Reporter: Kanak Biscuitwala
>
> We have potential use cases for disabling things at a local and a global level depending on the types of failure conditions. We need to review this algorithm and determine if the disable logic does what people intuitively expect it to.



--
This message was sent by Atlassian JIRA
(v6.2#6252)