[ 
https://issues.apache.org/jira/browse/HDDS-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hemant Kumar reassigned HDDS-9360:
----------------------------------

    Assignee: Hemant Kumar

> [snapshot] SnapshotDiff should not accept continuation token greater than the 
> length of the actual snapdiff
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-9360
>                 URL: https://issues.apache.org/jira/browse/HDDS-9360
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Snapshot
>            Reporter: Jyotirmoy Sinha
>            Assignee: Hemant Kumar
>            Priority: Major
>              Labels: newbie
>
> Steps :
>  * Create volume/bucket
>  * Create 1 key and create snapshot snap1
>  * Create 155 more keys and create snapshot snap160
>  * Execute snapshotDiff with continuation token 150
>  * Execute snapshotDiff with continuation token 200
> Observed behaviour - 
> SnapshotDiff lists till end of diff and gives next continuation token
> {code:java}
> # ozone sh snapshot diff -p 5 -t 150 vol1/buck1 snap1 snap160
> Difference between snapshot: snap1 and snapshot: snap160
> +    ./key156
> +    ./key157
> +    ./key158
> +    ./key159
> +    ./key160
> Next token: 155 {code}
> SnapshotDiff does not list any items in the diff when continuation token is 
> more than actual diff
> {code:java}
> # ozone sh snapshot diff -p 5 -t 200 vol1/buck1 snap1 snap160
> Difference between snapshot: snap1 and snapshot: snap160 {code}
> Expected behaviour -
> SnapshotDiff should reject when continuation token is more than actual diff. 
> Also when snapshotDiff has reached the end limit of diff, it should not 
> return any continuation token.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to