Return-Path: X-Original-To: apmail-helix-user-archive@minotaur.apache.org Delivered-To: apmail-helix-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7E96010544 for ; Thu, 11 Apr 2013 00:28:54 +0000 (UTC) Received: (qmail 52224 invoked by uid 500); 11 Apr 2013 00:28:54 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 52190 invoked by uid 500); 11 Apr 2013 00:28:54 -0000 Mailing-List: contact user-help@helix.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@helix.incubator.apache.org Delivered-To: mailing list user@helix.incubator.apache.org Received: (qmail 52181 invoked by uid 99); 11 Apr 2013 00:28:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Apr 2013 00:28:54 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nehzgnahz@gmail.com designates 209.85.210.170 as permitted sender) Received: from [209.85.210.170] (HELO mail-ia0-f170.google.com) (209.85.210.170) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Apr 2013 00:28:47 +0000 Received: by mail-ia0-f170.google.com with SMTP id j38so957615iad.29 for ; Wed, 10 Apr 2013 17:28:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=xjsfHycmw0miO6CmD6699TfJqVl6qLDAAB+siYy8zVk=; b=IvhN8D/X4LQ2qYQ8rUMkfAiPQikdB2skzjUTT0gfOfxtcLo+zQjwZgPjkUV8sO/RBx PE3zYiLFFOkTcp7N228zAxjl4c5UsT6AStLJHtNaIvCotwVGSAH0w0iIKO9teQHSS0RA T22UWr9K8xDyxnHAIIfpyK3bYGHdSJAlvDyk+/1G3TuZVay/ENMBfSOeBe1CqpSqy8TO 9toa4chQxKQaYLe7mAo8+TzGZt7Ql0EVPXZOrymn8GHucsK8fHvWNSQjdN/53/NUCfD/ uEUkSPFqs5sBFUnyMtV24dgecs/GZJQNvImFFQHUTMCP2/ZfgMMvC8qijywa7ibBQKZo ZUrQ== MIME-Version: 1.0 X-Received: by 10.50.6.3 with SMTP id w3mr14647458igw.76.1365640106770; Wed, 10 Apr 2013 17:28:26 -0700 (PDT) Received: by 10.42.117.136 with HTTP; Wed, 10 Apr 2013 17:28:26 -0700 (PDT) In-Reply-To: <516602EA.2020209@yahoo.com> References: <5165EAFB.4080806@yahoo.com> <516602EA.2020209@yahoo.com> Date: Wed, 10 Apr 2013 17:28:26 -0700 Message-ID: Subject: Re: Configuration Data change listeners From: Zhen Zhang To: user@helix.incubator.apache.org Content-Type: multipart/alternative; boundary=047d7bdc166e74873704da0add6c X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc166e74873704da0add6c Content-Type: text/plain; charset=ISO-8859-1 Thanks for pointing out that. The feature will be included in 0.6.1 release. Thanks, Jason On Wed, Apr 10, 2013 at 5:25 PM, Vinayak Borkar wrote: > It looks like this feature is not present in 0.6.0-incubating. Thanks for > the pointer. > > > > On 4/10/13 5:02 PM, Zhen Zhang wrote: > >> yes. >> >> HelixManager#**addConfigChangeListener(**ScopedConfigChangeListener >> listener, >> ConfigScopeProperty scope) registers a config change listener for >> different >> scopes (i.e. CLUSTER, RESOURCE, PARTITION) >> >> TestListenerCallback#**testBasic() has examples for using it. For >> example, >> the following line registers a cluster scope config change listener: >> manager.**addConfigChangeListener(**listener, >> ConfigScopeProperty.CLUSTER); >> >> Thank, >> Jason >> >> >> >> On Wed, Apr 10, 2013 at 3:43 PM, Vinayak Borkar wrote: >> >> Hi, >>> >>> >>> I see that HelixManager provides a way to set and get config information >>> related to Resources, Partitions and other things. >>> >>> Is there a way that changes to this information can be tracked by using >>> listeners? >>> >>> Thanks, >>> Vinayak >>> >>> >> > --047d7bdc166e74873704da0add6c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for pointing out that. The feature will be included= in 0.6.1 release.

Thanks,
Jason


On Wed, Apr 10,= 2013 at 5:25 PM, Vinayak Borkar <vborky@yahoo.com> wrote:
It looks like this feature is not present in= 0.6.0-incubating. Thanks for the pointer.



On 4/10/13 5:02 PM, Zhen Zhang wrote:
yes.

HelixManager#addConfigChangeListener(ScopedConfigChangeListen= er listener,
ConfigScopeProperty scope) registers a config change listener for different=
scopes (i.e. CLUSTER, RESOURCE, PARTITION)

TestListenerCallback#testBasic() has examples for using it. For exam= ple,
the following line registers a cluster scope config change listener:
manager.addConfigChangeListener(listener, ConfigScopeProperty= .CLUSTER);

Thank,
Jason



On Wed, Apr 10, 2013 at 3:43 PM, Vinayak Borkar <vborky@yahoo.com> wrote:

Hi,


I see that HelixManager provides a way to set and get config information related to Resources, Partitions and other things.

Is there a way that changes to this information can be tracked by using
listeners?

Thanks,
Vinayak




--047d7bdc166e74873704da0add6c--