[I] Surface foreign ExecutionPlan metrics via FFI (FFI_MetricsSet) [datafusion-python]

["timsaucer (via GitHub)" <gi...@apache.org>]

timsaucer opened a new issue, #1576:
URL: https://github.com/apache/datafusion-python/issues/1576

   ## Background
   
   `PyMetricsSet` currently wraps the native DataFusion `MetricsSet` only. When a foreign `ExecutionPlan` is imported through `FFI_ExecutionPlan` (for example a plan implemented in a separate Rust extension, Go, or another Python module), there is no FFI round-trip for metrics: ``plan.metrics()`` on such a foreign plan returns whatever the underlying implementation happens to populate, with no standard way for the foreign side to surface DataFusion-style metrics back across the boundary.
   
   ## Why deferred
   
   There is no `FFI_MetricsSet` struct in the upstream `datafusion-ffi` crate at v54 to wrap; this is a pipeline-symmetry concern rather than a feature gap with a clear upstream target. No open user requests at the time of audit. Filed for tracking so that when upstream lands FFI metrics support, the Python bindings can pick it up immediately. The accepted path is probably: upstream adds `FFI_MetricsSet` and threads it through `FFI_ExecutionPlan::metrics`; the Python bindings then expose a `from_pycapsule` helper on `MetricsSet` analogous to the other `*Exportable` patterns.


-- 
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: github-unsubscribe@datafusion.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org