Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Bug
-
1.4.0, 2.0.0
Description
In the Open Keys API for Recon
<RECON ENDPOINT>/api/v1/keys/open?includeFso=false&includeNonFso=true&limit=1000
the value for the path and the key are swapped.
This is present for both fso and nonFso types.
So we should provide the path as the 'key' and the key as the 'path' in the response.
Please refer to attached response for this behaviour:
{ "lastKey": "/vol1/bukc2/test5/113040107766874114", "replicatedDataSize": 30000000000, "unreplicatedDataSize": 10000000000, "nonFSO": [ { "key": "/vol1/bukc2/test5/113040107766874114", "path": "test5", "inStateSince": 1724855160012, "size": 10000000000, "replicatedSize": 30000000000, "replicationInfo": { "replicationFactor": "THREE", "requiredNodes": 3, "replicationType": "RATIS" }, "creationTime": 1724862833434, "modificationTime": 1724862833434, "isKey": true } ], "status": "OK" }
Attachments
Issue Links
- links to