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
Report DataFusion operator metrics in IcebergTableScan #2364
Is your feature request related to a problem or challenge?
IcebergTableScan does not implement ExecutionPlan::metrics(), so EXPLAIN ANALYZE shows an empty metrics=[] on the scan line while every other operator in the plan reports its cost.
This makes query profiling against Iceberg tables blind on the scan, and prevents quantifying optimizations that touch the scan.
Reproducer:EXPLAIN ANALYZE SELECT * FROM t WHERE foo = 1:
Wire BaselineMetrics + ExecutionPlanMetricsSet into IcebergTableScan, same pattern as ParquetExec.
Scope limited to the two default metrics (elapsed_compute, output_rows). bytes_scanned is a natural follow-up once #2349 lands: its ScanMetrics counter can be exposed as a custom DataFusion metric in a separate PR.
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.
Activity
github-actions commentedon Oct 22, 2026
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.
github-actions commentedon Nov 6, 2026
This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'