apurtell opened a new pull request, #2520: URL: https://github.com/apache/phoenix/pull/2520
The three effectively plan level estimate columns become part of the top-of-plan disclosure. Today `PhoenixStatement.ExecutableExplainStatement.compilePlan` rebuilds the same `EST_BYTES_READ` / `EST_ROWS_READ` / `EST_INFO_TS` cells on every `planSteps` row, so a reader scanning the result set sees them repeated on every operator and reasonably assumes they are per-step. The three `PhoenixKeyValueUtil.newKeyValue(...)` calls for `EXPLAIN_PLAN_BYTES_ESTIMATE`, `EXPLAIN_PLAN_ROWS_ESTIMATE`, and `EXPLAIN_PLAN_ESTIMATE_INFO_TS` are hoisted. Subsequent rows carry just the `EXPLAIN_PLAN_COLUMN` cell and the missing estimate cells surface as SQL `NULL`. The `RowProjector` is unchanged, and the whole block is skipped when `getEstimated*ToScan()` returns null. The three plan-total fields are added to `ExplainPlanAttributes`. Co-authored-by: Claude Opus 4.8[1m] <[email protected]> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
