apache / apache/datafusion-python

Surface foreign ExecutionPlan metrics via FFI (FFI_MetricsSet)

Open
#1,576 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
604
Forks
174
Avg merge
1d 7h
Merged PRs (30d)
4

Description

## 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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.