ordeq_common 2.2.0

Frequently used IOs and Hooks for Ordeq projects

Welcome to Ordeq!

Ordeq is a framework for developing data pipelines. It simplifies IO and modularizes pipeline logic. Ordeq elevates your proof-of-concept to a production-grade pipelines. See the introduction for an easy-to-follow example of how Ordeq can help.

Installation

Ordeq is available under MIT license. Please refer to the license and notice for more details.

To install Ordeq, run:

uv pip install ordeq

Integrations

Ordeq integrates seamlessly with existing tooling. It provides integrations with many popular libraries out of the box. You can install them as needed. For example, for reading and writing data with Pandas, install the ordeq-pandas package:

uv pip install ordeq-pandas

Some of the available integrations:

Data processing

Pandas	Spark	Numpy	Polars	Ibis	Joblib	HuggingFace
st	Requests	Pydantic	DuckDB	NetworkX	TOML	PyMuPDF

Plotting

Matplotlib

Altair

Plotly Express

Cloud storage

Google Cloud Storage

Azure Storage Blob

AWS S3

Boto3

Have a look at the package overview and API reference for a list of available packages.

Documentation

Documentation is available at https://ing-bank.github.io/ordeq/.

Why consider Ordeq?

• Ordeq is the GenAI companion: it gives your project structure and consistency, such that GenAI can thrive
• It offers seamless integrations with existing data & ML tooling, such as Spark, Pandas, Pydantic and PyMuPDF, and adding new integrations is trivial
• It's actively developed and trusted by data scientists, engineers, analysts and machine learning engineers at ING

Learning Ordeq

To learn more about Ordeq, check out the following resources:

• See how Ordeq can help your project in the introduction
• Check out the core concepts to learn how to use Ordeq
• Explore the example projects to see how Ordeq is used

Acknowledgements

Ordeq builds upon design choices and ideas from Kedro and other frameworks. It has been developed at ING, with contributions from various individuals. Please refer to the acknowledgements section in the documentation for more details.