This is an automated email from the ASF dual-hosted git repository.

sshenoy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone.git


The following commit(s) were added to refs/heads/master by this push:
     new b5fd0ce628 HDDS-9268. [Snapshot] Update list of snapshot apis to 
include lsDiff details in docs. (#5278)
b5fd0ce628 is described below

commit b5fd0ce628e7cf611babddffff067675965ef7c5
Author: jyotirmoy-gh <[email protected]>
AuthorDate: Wed Sep 13 11:48:25 2023 +0530

    HDDS-9268. [Snapshot] Update list of snapshot apis to include lsDiff 
details in docs. (#5278)
---
 hadoop-hdds/docs/content/feature/Snapshot.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/hadoop-hdds/docs/content/feature/Snapshot.md 
b/hadoop-hdds/docs/content/feature/Snapshot.md
index d0223f12cd..414561269a 100644
--- a/hadoop-hdds/docs/content/feature/Snapshot.md
+++ b/hadoop-hdds/docs/content/feature/Snapshot.md
@@ -50,9 +50,13 @@ ozone sh snapshot delete [-hV] <bucket> <snapshotName>
 ```shell
 ozone sh snapshot diff [-chV] [-p=<pageSize>] [-t=<continuation-token>] 
<bucket> <fromSnapshot> <toSnapshot>
 ```
-
 SnapshotDiff CLI/API is asynchronous. The first time the API is invoked, OM 
starts a background thread to calculate the SnapshotDiff, and returns "Retry" 
with suggested duration for the retry operation. Once the SnapshotDiff is 
computed, this API returns the diffs in multiple Pages. Within each Diff 
response, OM also returns a continuation token for the client to continue from 
the last batch of Diff results.  This API is safe to be called multiple times 
for a given snapshot source and de [...]
 
+* List SnapshotDiff Jobs: List all snapshotDiff jobs of a given bucket 
+```shell
+ozone sh snapshot listDiff [-ahV] [-s=<jobStatus>] <bucket>
+```
+
 ## Architecture
 
 Ozone Snapshot architecture leverages the fact that data blocks once written, 
remain immutable for their lifetime. These data blocks are reclaimed only when 
the object key metadata that references them, is deleted from the Ozone 
namespace. All of this Ozone metadata is stored on the OM nodes in the Ozone 
cluster. When a user takes a snapshot of an Ozone bucket, internally the system 
takes snapshot of the Ozone metadata in OM nodes. Since Ozone doesn't allow 
updates to datanode blocks, in [...]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to