Hi Santi, you are right. The property store obtained from HelixManager is not registering with any paths. You should construct your own property store.
On Mon, Aug 5, 2013 at 9:57 AM, Santiago Perez <[email protected]> wrote: > I'm not following. When calling subscribe I'm providing relative path, the > problem is that the store obtained from the HelixManager is not listening > to subscribed to anything and never will be. > > > On Mon, Aug 5, 2013 at 1:54 PM, kishore g <[email protected]> wrote: > > > You should probably provide only relative path, not absolute. If thats > not > > the case, we should fix it. > > > > > > On Mon, Aug 5, 2013 at 9:51 AM, Santiago Perez <[email protected]> > > wrote: > > > > > I see, but I'm obtaining the property store via the HelixManager. > Should > > I > > > be constructing it myself? > > > > > > > > > On Mon, Aug 5, 2013 at 1:43 PM, Zhen Zhang <[email protected]> > wrote: > > > > > > > yes. you need to construct with a list of paths. subscribe () works > > with > > > > any sub paths of the constructed paths. > > > > On Aug 5, 2013 9:34 AM, "Santiago Perez" <[email protected]> > wrote: > > > > > > > > > Hey guys, > > > > > > > > > > I'm trying to rely on ZkHelixPropertyStore.subscribe(String, > > > > > HelixPropertyListener) to listen for changes to certain paths in > the > > > > > property store but I'm never getting any callbacks. > > > > > > > > > > Looking into the code I noticed that > > > HelixManager.getHelixPropertyStore() > > > > > is creating a ZkHelixPropertyStore with null in the subscribedPaths > > > > > argument. This prevents the event thread from being started and in > > fact > > > > the > > > > > log confirms that with line: > > > > > "ZkCachePaths is null or empty. Will not start ZkCacheEventThread" > > > > > > > > > > So everything seems to indicate that this is the cause why I will > > never > > > > get > > > > > a callback on property store changes. > > > > > > > > > > Thanks, > > > > > Santiago > > > > > > > > > > > > > > >
