[
https://issues.apache.org/jira/browse/HDFS-12998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365573#comment-16365573
]
Tsz Wo Nicholas Sze commented on HDFS-12998:
--------------------------------------------
In the 001 patch, next() set thisListing = null and throws
NoSuchElementException when hasNext() == false. After that, hasNext() will
returns true again since (thisListing == null). It probably is a bug.
> SnapshotDiff - Provide an iterator-based listing API for calculating
> snapshotDiff
> ---------------------------------------------------------------------------------
>
> Key: HDFS-12998
> URL: https://issues.apache.org/jira/browse/HDFS-12998
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Attachments: HDFS-12998.001.patch
>
>
> Currently , SnapshotDiff computation happens over multiple rpc calls to
> namenode depending on the no of snapshotDiff entries where each rpc call
> returns at max 1000 entries by default . Each "getSnapshotDiffreportListing"
> call to namenode returns a partial snapshotDiffreportList which are all
> combined and processed at the client side to generate a final
> snapshotDiffreport. There can be cases where SnapshotDiffReport can be huge
> and in situations as such , the rpc calls to namnode should happen on demand
> at the client side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
