[
https://issues.apache.org/jira/browse/ZOOKEEPER-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796504#comment-15796504
]
ASF GitHub Bot commented on ZOOKEEPER-2565:
-------------------------------------------
GitHub user hanm opened a pull request:
https://github.com/apache/zookeeper/pull/140
ZOOKEEPER-2565: Fix ServerConfigTest#testValidArguments test case.
ServerConfig.getDataDir returns type String in branch-3.4 but return type
File in branch-3.5 and master. So we need to deal with this difference
accordingly in our test.
This PR is intended to be merged in master, branch-3.5, and branch-3.4.
@rakeshadr PTAL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hanm/zookeeper ZOOKEEPER-2565
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/140.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #140
----
commit 48f099c5419ff526934a7c7ff7c0d89ced970e09
Author: Michael Han <[email protected]>
Date: 2017-01-03T22:29:39Z
ZOOKEEPER-2565: Fix ServerConfigTest#testValidArguments test case failures
for both branch-3.4 and branch-3.5, master.
ServerConfig.getDataDir returns type String in branch-3.4 but return type
File in branch-3.5 and master. So we need to deal with this difference
accordingly in our test.
----
> listquota <path> should display the quota even it is set on parent/child node
> -----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2565
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2565
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.1
> Reporter: Rakesh Kumar Singh
> Assignee: kevin.chen
> Priority: Minor
>
> listquota <path> should display the quota even it is set on parent/child
> node. As of now if we have a parent-child hierarchy for example n1->n2->n3
> and quota is set for n2. If we try to get quota details on n1 and n3 using
> listquota, it says no quota set but if try to set the quota on those nodes it
> fails saying quota is already set on parent node...
> So listquota should fetch the quota set on any node in hierarchy with exact
> path (on which quota is set) even though this api is called on any other node
> in that hierarchy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
