This repository was archived by the owner on Dec 13, 2023. It is now read-only.
This repository was archived by the owner on Dec 13, 2023. It is now read-only.
Sub-objects at depth 3+ missing in HTTP response description #106
Description
Compare get_api_collection_figures.md
to https://www.arangodb.com/docs/3.4/http/collection-getting.html#return-statistics-for-a-collection
The response format is deeply nested, e.g:
- figures
- dead
- count
- size
- dead
count and size are absent in the docs, as well as other nested objects at level 3:
The definition looks okay:
@RESTSTRUCT{dead,collection_figures,object,required,collection_figures_dead} the items waiting to be swept away by the cleaner @RESTSTRUCT{count,collection_figures_dead,integer,required,int64} The number of dead documents. This includes document versions that have been deleted or replaced by a newer version. Documents deleted or replaced that are contained the write-ahead log only are not reported in this figure. @RESTSTRUCT{size,collection_figures_dead,integer,required,int64} The total size in bytes used by all dead documents. @RESTSTRUCT{deletion,collection_figures_dead,integer,required,int64} The total number of deletion markers. Deletion markers only contained in the write-ahead log are not reporting in this figure.