Mailing-List: contact user-help@curator.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Curator namespaces
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
In-Reply-To: 
 <CANykdub6xWNn7u7j076+zPCt=8dLC_WFbbD3H0v2h2boEMkD_w@mail.gmail.com>
Date: Sun, 20 Oct 2013 17:00:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECFADABA-5EA7-49C3-8BD8-D0242C2F3E06@jordanzimmerman.com>
References: 
 <CANykdub6xWNn7u7j076+zPCt=8dLC_WFbbD3H0v2h2boEMkD_w@mail.gmail.com>
To: user@curator.incubator.apache.org

If I understand what you're saying that would be a bug. If you can, =
please provide a test case and open an issue in Jira.

-Jordan

On Oct 20, 2013, at 4:52 PM, Cameron McKenzie <mckenzie.cam@gmail.com> =
wrote:

> Not sure if I'm missing something, but it appears that there is a =
difference in functionality between defining a namespace during using =
the CuratorFrameworkFactory.builder().namespace("bla") method, and =
calling usingNamespace("bla") on an instance of the CuratorFramework =
itself.
>=20
> Both seem to create nodes correctly in ZooKeeper, but the paths for =
the events are inconsistent. If you using the Builder approach, the =
paths in the events do not include the namespace. If you use the =
CuratorFramework usingNamespace() approach, then the namespaces do =
appear in the event path.
>=20
> Is this by design? Or just a side effect?
> cheers
> Cam
>=20
>=20