You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/api/meta_service.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -256,6 +256,9 @@ Example response:
256
256
},
257
257
"items": [
258
258
{
259
+
"status": {
260
+
"code": "OK"
261
+
},
259
262
"request_index": 0,
260
263
"block_key": 123,
261
264
"prev_block_key": "",
@@ -287,6 +290,9 @@ Example response:
287
290
]
288
291
},
289
292
{
293
+
"status": {
294
+
"code": "OK"
295
+
},
290
296
"request_index": 1,
291
297
"block_key": 456,
292
298
"locations": [
@@ -299,4 +305,4 @@ Example response:
299
305
}
300
306
```
301
307
302
-
This diagnostic API returns raw metadata for every unmasked requested key. It does not apply location selection, data-file existence filtering, or lazy prune.
308
+
This diagnostic API returns raw metadata for every unmasked requested key. It does not apply location selection, data-file existence filtering, or lazy prune.`prev_block_key` is a convenience projection of `properties["BP#prev_key"]`; the raw property is intentionally retained. A missing key is reported as a successful item with `CLS_NOT_FOUND`. Backend or deserialization failures are reported in that item's `status` while other successful items are still returned. If every item fails to read, the request returns an overall error.
0 commit comments