Return-Path: X-Original-To: apmail-curator-user-archive@minotaur.apache.org Delivered-To: apmail-curator-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 BD8D910C7C for ; Mon, 3 Feb 2014 21:04:48 +0000 (UTC) Received: (qmail 56476 invoked by uid 500); 3 Feb 2014 21:04:48 -0000 Delivered-To: apmail-curator-user-archive@curator.apache.org Received: (qmail 56393 invoked by uid 500); 3 Feb 2014 21:04:47 -0000 Mailing-List: contact user-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@curator.apache.org Delivered-To: mailing list user@curator.apache.org Received: (qmail 56385 invoked by uid 99); 3 Feb 2014 21:04:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Feb 2014 21:04:47 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [198.203.175.175] (HELO mail16.uhc.com) (198.203.175.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Feb 2014 21:04:42 +0000 X-IronPort-AV: E=Sophos;i="4.95,774,1384322400"; d="scan'208,217";a="1313891123" Received: from irmelr24.uhc.com (HELO mail16.uhc.com) ([10.177.104.170]) by mail18.uhc.com with ESMTP; 03 Feb 2014 15:04:20 -0600 X-IronPort-AV: E=Sophos;i="4.95,774,1384322400"; d="scan'208,217";a="1313891120" X-CONF-FOOTER: True Received: from apsep0947.ms.ds.uhc.com ([10.179.216.42]) by mail16.uhc.com with ESMTP; 03 Feb 2014 15:04:20 -0600 Received: from apswp0428.ms.ds.uhc.com ([fe80::7cb7:a560:d0b0:bc2d]) by APSEP0947.ms.ds.uhc.com ([fe80::4923:b25a:771b:43c4%10]) with mapi id 14.03.0146.000; Mon, 3 Feb 2014 15:04:20 -0600 From: "Lavoie, John L" To: "user@curator.apache.org" Subject: Path Cache Recipe and traversing child nodes Thread-Topic: Path Cache Recipe and traversing child nodes Thread-Index: Ac8hIlsWaGzKvLx8Tu+5+HBoPDTjbQ== Date: Mon, 3 Feb 2014 21:04:19 +0000 Message-ID: <0C075FF7C527504E8058F4102A4BAFC514A9CC@APSWP0428.ms.ds.uhc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.204.2.151] Content-Type: multipart/alternative; boundary="_000_0C075FF7C527504E8058F4102A4BAFC514A9CCAPSWP0428msdsuhcc_" MIME-Version: 1.0 X-IP-VFilter-R: R X-Virus-Checked: Checked by ClamAV on apache.org --_000_0C075FF7C527504E8058F4102A4BAFC514A9CCAPSWP0428msdsuhcc_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi, I'm brand new to Zookeeper and am trying Curator to help get a jump start. = I'm looking through the curator recipes and the Path Cache seems like a re= ally good fit for me. I want to post the state of my currently executing Cascading jobs to zookee= per so that we can centrally query them from a different system. The znode= hierarchy might look something like this: /my/app/ -/otherdata/ -/jobstatus/ --/activejob1 --/activejob2 I've set up a PathChildrenCache instance to monitor /my/app/ and I'm not se= eing any updates when I write values to the jobstatus node. I need to chan= ge my reading app to monitor /my/app/jobstatus. It looks like the PathChil= drenCache and the Path Cache recipe are not capable of iterating over child= ren within the main node that it is monitoring. Is that true? Is there a w= ay around this without having to monitor multiple nodes for updates or is t= hat an inherent design to Curator/ZK? I don't even see an easy way to traverse the child nodes through the PathCa= che Example if I try to change the list() method to recursively walk the tr= ee. I must be missing something in the API here, right? John Lavoie This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. --_000_0C075FF7C527504E8058F4102A4BAFC514A9CCAPSWP0428msdsuhcc_ Content-Type: text/html; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable

Hi,

 

I’m brand new to Zookeeper and am trying Curat= or to help get a jump start.  I’m looking through the curator re= cipes and the Path Cache seems like a really good fit for me.


I want to post the state of my currently executing Cascading jobs to zookee= per so that we can centrally query them from a different system.  The = znode hierarchy might look something like this:

 

/my/app/

-/otherdata/

-/jobstatus/

--/activejob1

--/activejob2

 

I’ve set up a PathChildrenCache instance to mo= nitor /my/app/ and I’m not seeing any updates when I write values to = the jobstatus node.  I need to change my reading app to monitor /my/ap= p/jobstatus.  It looks like the PathChildrenCache and the Path Cache recipe are not capable of iterating over children within th= e main node that it is monitoring.  Is that true? Is there a way aroun= d this without having to monitor multiple nodes for updates or is that an i= nherent design to Curator/ZK?

 

I don’t even see an easy way to traverse the c= hild nodes through the PathCache Example if I try to change the list() meth= od to recursively walk the tree.  I must be missing something in the A= PI here, right?

 

John Lavoie


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended<= br> recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

<= /body> --_000_0C075FF7C527504E8058F4102A4BAFC514A9CCAPSWP0428msdsuhcc_--