[
https://issues.apache.org/jira/browse/ZOOKEEPER-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796541#comment-15796541
]
Hadoop QA commented on ZOOKEEPER-2565:
--------------------------------------
+1 overall. GitHub Pull Request Build
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/182//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/182//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/182//console
This message is automatically generated.
> 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)
