[
https://issues.apache.org/jira/browse/ZOOKEEPER-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081985#comment-15081985
]
Chris Nauroth commented on ZOOKEEPER-1962:
------------------------------------------
bq. One minor improvement might be that instead of accumulating the full set of
children in a List<String>, we should do incremental printing of the results
without the full list.
I also was concerned about running out of memory on the client because of this.
The trouble is that incremental printing would conflict with the current
behavior of sorted output, as enforced later in {{LsCommand#printChildren}}.
Results returned from the server are unsorted {{HashMap}} keys, so it looks
like we've been relying on a client-side sort for consistent sorted results. I
assume we need to maintain that sorting as the default behavior for
backwards-compatibility. Maybe we just say that the {{-R}} option is
inherently not sorted?
> Add a CLI command to recursively list a znode and children
> ----------------------------------------------------------
>
> Key: ZOOKEEPER-1962
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1962
> Project: ZooKeeper
> Issue Type: New Feature
> Components: java client
> Affects Versions: 3.4.6
> Reporter: Gautam Gopalakrishnan
> Assignee: Gautam Gopalakrishnan
> Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1962.diff, ZOOKEEPER-1962_v2.patch,
> ZOOKEEPER-1962_v3.patch, ZOOKEEPER-1962_v4.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When troubleshooting applications where znodes can be multiple levels deep
> (eg. HBase replication), it is handy to see all child znodes recursively
> rather than run an ls for each node manually.
> So I propose adding an option to the "ls" command (-r) which will list all
> child nodes under a given znode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
