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
{{ message }}
Repository navigation
Commit 130ee02
Browse filesBrowse the repository at this point in the historyBrowse files
|`scan_io_data_bytes`| Bytes returned to the Parquet reader for projected data-page ranges. |
90
+
|`scan_io_metadata_bytes`| Bytes returned for footer prefetches, page indexes, and Bloom filters. A footer prefetch can also contain unused data bytes. |
91
+
|`scan_io_footer_reads`| Storage reads of complete serialized footer payloads, counted once per metadata open. Plaintext payloads must decode successfully; encrypted payloads are counted before key retrieval/decryption, even if those later fail. |
92
+
|`scan_io_footer_bytes`| Serialized footer payload bytes, excluding the final eight-byte trailer. These bytes are already included in `scan_io_metadata_bytes`. |
93
+
|`scan_io_object_store_get_calls`| Nonempty GET operations at the native remote `ObjectStore` API, after range coalescing. Does not count transport retries or HEAD requests. |
94
+
|`scan_io_object_store_get_requested_bytes`| Requested coalesced range bytes at that API. A failed or partly consumed request can contribute requested bytes without the same number of response bytes. |
95
+
|`scan_io_object_store_response_bytes_read`| Response bytes actually consumed at that API, including bytes fetched between coalesced ranges. Not HTTP wire bytes. |
96
+
|`scan_io_metadata_cache_hits`| Successful, cache-eligible metadata opens requiring no storage reads. |
97
+
|`scan_io_metadata_cache_misses`| Successful, cache-eligible metadata opens requiring storage reads. Failed opens and encrypted opens, which bypass this shared cache, increment neither cache counter. |
98
+
99
+
Reader-level and object-store bytes are two views of the same reads; do not add them together.
100
+
Likewise, footer bytes are a subset of metadata bytes, not a third reader-level category. A warm
101
+
metadata-cache hit contributes no new metadata or footer I/O. A valid plaintext footer followed by
102
+
a page-index failure still contributes footer bytes; an invalid plaintext footer does not.
103
+
104
+
Remote counters follow the backend selected during object-store construction, including native
0 commit comments