This release is a pre-release and may not be stable for production use.
Flyte Pandera Plugin
flyteplugins-pandera adds support for pandera.typing.pandas.DataFrame, pandera.typing.polars.DataFrame / LazyFrame, and pandera.typing.pyspark_sql.DataFrame in Flyte v2.
Install:
pip install flyteplugins-pandera 'pandera[pandas]' # pandas only
pip install flyteplugins-pandera 'pandera[polars]' flyteplugins-polars # Polars + structured dataset I/O
pip install flyteplugins-pandera 'pandera[pyspark]' flyteplugins-spark # PySpark SQL + parquet I/O
For PySpark, structured dataset serialization uses Flyte’s DataFrameTransformerEngine parquet handlers from flyteplugins-spark (register Spark encoders/decoders alongside this plugin).
At runtime, the plugin:
- delegates dataframe IO to Flyte's
DataFrameTransformerEngine, - validates data with pandera schemas, and
- writes a validation report to
flyte.report.
Validation always runs on every encode/decode. Report tabs are suppressed automatically when Flyte is only moving literals across a nested-task boundary (parent task encoding child inputs, or materializing a child’s outputs inside the parent). The SDK sets TaskContext.in_driver_literal_conversion on the active task (check with flyte.ctx() when non-None, then .in_driver_literal_conversion) so you see one report per dataframe on the task that actually produced or consumed it as task body I/O, not extra tabs on the orchestrating “driver” task.
Troubleshooting
If logs show “Unsupported Type pandera.typing… Flyte will default to use PickleFile”, the pandera transformer was not registered:
- Install the plugin in every environment (local runner and task image):
pip install flyteplugins-pandera. - Flyte loads
flyte.plugins.typesduringflyte.initialize()and on firstTypeEngineuse; confirm the distribution is installed (import importlib.metadata as m; print(list(m.entry_points(group="flyte.plugins.types")))). - Import order: import your
pandera.typing.*modules before plugin registration runs in files that run early (tests,__init__.py). Loading the plugin before pandera can leave two differentpandera.typing.pandas.DataFrame(or polars container) class objects in the process;TypeEnginewould only know about one of them, so annotations on the other fall through to pickle / the generic handler.
Metadata
Release files for flyteplugins-pandera 2.12.5a0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flyteplugins_pandera-2.12.5a0-py3-none-any.whl | Python 3 | none | any | Details for flyteplugins_pandera-2.12.5a0-py3-none-any.whl |
Release files / flyteplugins_pandera-2.12.5a0-py3-none-any.whl
| Download URL | flyteplugins_pandera-2.12.5a0-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ac2f55eb863a65d1bf2a4eb760b6f44fc30eefbbebe0867ea14b3a4b08951f7
|
|
BLAKE2b-256 checksum How to use checksums |
52167647e420ed5b36fd0daba7c2b320398ac91f7a20f4e3d55391193889c101
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.18
|
Security for flyteplugins-pandera 2.12.5a0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.