[
https://issues.apache.org/jira/browse/CURATOR-586?focusedWorklogId=764617&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-764617
]
ASF GitHub Bot logged work on CURATOR-586:
------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Apr/22 05:04
Start Date: 30/Apr/22 05:04
Worklog Time Spent: 10m
Work Description: tisonkun commented on PR #377:
URL: https://github.com/apache/curator/pull/377#issuecomment-1113916643
@nryanov as @cammckenzie mentioned in the JIRA ticket, Curator handles
nullity correctly internally. You may provide a real-world use case to make
this change. Otherwise, it can be closed as unnecessary.
Issue Time Tracking
-------------------
Worklog Id: (was: 764617)
Time Spent: 1h (was: 50m)
> NamespaceFacade return null if namespace is empty
> -------------------------------------------------
>
> Key: CURATOR-586
> URL: https://issues.apache.org/jira/browse/CURATOR-586
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Reporter: Nikita Ryanov
> Priority: Trivial
> Time Spent: 1h
> Remaining Estimate: 0h
>
> According to java doc framework should return empty string if namespace is
> empty instead of null:
>
> {code:java}
> /**
> * Return the current namespace or "" if none
> *
> * @return namespace
> */
> public String getNamespace();
> {code}
>
> If namespace is claimed from CuratorFramework client directly all is ok, but
> if NamespaceFacade is used then null is returned.
> How to reproduce:
> {code:java}
> RetryPolicy policy = ...;
> CuratorFramework client =
> CuratorFrameworkFactory.newClient("connectionString", policy);
> CuratorFramework clientWithNamespaceFacade = client.usingNamespace(null);
> clientWithNamespaceFacade.getNamespace(); // <- expected "", but got null
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
