From 31f00624dd3977250a9ab753f84c369207e097ce Mon Sep 17 00:00:00 2001
From: Nikhil Sinha <nikhil.sinha@parseable.com>
Date: Tue, 11 Nov 2025 18:20:36 -0500
Subject: [PATCH] fix: bytes scanned in query

instead of using file_size from manifest -- which is size of json
we should use ingestion_size -- which is compressed size
---
 src/query/stream_schema_provider.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/query/stream_schema_provider.rs b/src/query/stream_schema_provider.rs
index b3907a9e9..1d8163fae 100644
--- a/src/query/stream_schema_provider.rs
+++ b/src/query/stream_schema_provider.rs
@@ -339,13 +339,13 @@ impl StandardTableProvider {
                 mut file_path,
                 num_rows,
                 columns,
-                file_size,
+                ingestion_size,
                 ..
             } = file;
 
             // Track billing metrics for files scanned in query
             file_count += 1;
-            total_file_size += file_size;
+            total_file_size += ingestion_size;
 
             // object_store::path::Path doesn't automatically deal with Windows path separators
             // to do that, we are using from_absolute_path() which takes into consideration the underlying filesystem