zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2260) Paginated getChildren call
Date Fri, 27 Jan 2017 20:30:25 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843449#comment-15843449

Hadoop QA commented on ZOOKEEPER-2260:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 8771ffdaacb87126a485ae740558f6a288ab980b.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 8 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    -1 javac.  The patch appears to cause tar ant target to fail.

    -1 findbugs.  The patch appears to cause Findbugs (version 3.0.1) to fail.

    +1 release audit.  The applied patch does not increase the total number of release audit

    -1 core tests.  The patch failed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3572//testReport/
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3572//console

This message is automatically generated.

> Paginated getChildren call
> --------------------------
>                 Key: ZOOKEEPER-2260
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2260
>             Project: ZooKeeper
>          Issue Type: New Feature
>    Affects Versions: 3.4.6, 3.5.0
>            Reporter: Marco P.
>            Assignee: Marco P.
>              Labels: api, features
>             Fix For: 3.5.3, 3.6.0
>         Attachments: ZOOKEEPER-2260.patch, ZOOKEEPER-2260.patch
> Add pagination support to the getChildren() call, allowing clients to iterate over children
N at the time.
> Motivations for this include:
>   - Getting out of a situation where so many children were created that listing them
exceeded the network buffer sizes (making it impossible to recover by deleting)[1]
>  - More efficient traversal of nodes with large number of children [2]
> I do have a patch (for 3.4.6) we've been using successfully for a while, but I suspect
much more work is needed for this to be accepted. 
> [1] https://issues.apache.org/jira/browse/ZOOKEEPER-272
> [2] https://issues.apache.org/jira/browse/ZOOKEEPER-282

This message was sent by Atlassian JIRA

View raw message