curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <>
Subject [jira] [Resolved] (CURATOR-68) Namespace is not stripped off events generated via a NamspaceFacade
Date Mon, 21 Oct 2013 13:41:42 GMT


Jordan Zimmerman resolved CURATOR-68.

       Resolution: Fixed
    Fix Version/s:     (was: awaiting-response)
         Assignee: Jordan Zimmerman

There's no way to make this work as there is only one event watcher. Therefore, I've changed
getCuratorListenable() in the NamespaceFacade to throw UnsupportedOperationException. I'm
not thrilled by this "fix" but it's the only thing that makes sense.

> Namespace is not stripped off events generated via a NamspaceFacade
> -------------------------------------------------------------------
>                 Key: CURATOR-68
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.2.0-incubating
>         Environment: Should be reproducable in any environment. Has been reproduced running
on Windows 7 and Solaris 10.
>            Reporter: Cameron McKenzie
>            Assignee: Jordan Zimmerman
>            Priority: Minor
>              Labels: namespace
>             Fix For: 2.3.0
>         Attachments:
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> When a namespace is defined via the CuratorFrameworkFactory.Builder methods, paths for
events generated by the CuratorFramework have the namespace stripped off them.
> When using a NamespaceFacade, the paths for generated event paths include the namespace.
> This appears to be due to the implementation of the Watcher() interface in the constructor
of the CuratorFrameworkImpl class. It attempts to remove the namespace from events before
passing them to CuratorListener instances. In the case where the namespace is defined by the
builder (and is thus part of the base CuratorFramework instance) this works fine. In the case
where a NamespaceFacade is being used then the namespace of the base CuratorFramework instance
is used instead of the namespace of the NamespaceFacade).
> I will attach a simple test case to reproduce

This message was sent by Atlassian JIRA

View raw message