datafusion.operator.output_rows
Rows output by operatorDimensions:None
Interface Metrics (3)
Dimensions:None
Dimensions:None
Sources
Technical Annotations (41)
Configuration Parameters (4)
datafusion.execution.batch_sizerecommended: 8192datafusion.execution.coalesce_batchesrecommended: true/sys/kernel/mm/transparent_hugepage/enabledrecommended: neverenforce_batch_size_in_joinsrecommended: enabledError Signatures (1)
output_rows=0log patternCLI Commands (2)
EXPLAIN ANALYZE SELECT * FROM t1 LEFT ANTI JOIN (SELECT * FROM t2 WHERE k <> 1) t2 ON t1.k = t2.kdiagnosticdatafusion-cli -c "select sum(l_extendedprice) / 7.0 as avg_yearly from lineitem, part where p_partkey = l_partkey and p_brand = 'Brand#23' and p_container = 'MED BOX' and l_quantity < (select 0.2 * avg(l_quantity) from lineitem where l_partkey = p_partkey);"diagnosticTechnical References (34)
dynamic partitioningconceptskipped_aggregation_rows metriccomponentCoalesceBatchesStreamcomponentHashJoincomponentMutableArrayDatacomponentarrow_select::concatcomponentBatchSplittercomponentMemoryPoolcomponentMemoryReservationcomponentRecordBatchcomponentNestedLoopJoinExeccomponentrecord batchconceptprobe-sideconceptbuild-sideconceptbatch_sizeconfiguration parameterCoalesceBatchesExeccomponentBatchCoalescercomponentSortMergeJoincomponentHashJoinExeccomponentLEFT ANTI JOINconceptRIGHT ANTI JOINconceptfast-path optimizationconceptnested_loop_join.rsfile pathbatch_transformercomponentColumnStatisticscomponentTable Statisticscomponentjoin cardinality estimationconceptfilter selectivityconceptTPC-Hconceptbuild sideconceptprobe sideconceptstar schemaconceptright deep treeconceptEXPLAIN ANALYZEcomponentRelated Insights (11)
Streaming query throughput degradation after DataFusion 50 upgradewarning
▸
Tiny output batches cause excessive metadata memory consumptionwarning
▸
Partial aggregation inefficiency with high cardinality causes performance degradationwarning
▸
CoalesceBatches spends 17% of join execution time concatenating small filtered batcheswarning
▸
Cascaded joins produce oversized RecordBatches causing OOMcritical
▸
Nested loop join creates excessive memory usage through oversized record batcheswarning
▸
Join operators produce non-uniform batch sizes causing memory and performance issueswarning
▸
Hash join with empty build side reports zero output rows despite producing datawarning
▸
Nested loop join produces massive intermediate result sets consuming memorywarning
▸
Join disasters can occur without proper join reordering and statisticscritical
▸
Suboptimal join order causes 60% query performance degradation on multi-table joinswarning
▸