https://github.com/noklam/kedro-softfail-runner

A custom implemnetion of Kedro Runner to support softfailing
https://github.com/noklam/kedro-softfail-runner

Last synced: about 2 months ago
JSON representation

A custom implemnetion of Kedro Runner to support softfailing

• Host: GitHub
• URL: https://github.com/noklam/kedro-softfail-runner
• Owner: noklam
• License: apache-2.0
• Created: 2023-10-24T13:12:52.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2023-11-21T07:10:24.000Z (about 1 year ago)
• Last Synced: 2024-04-23T23:47:01.253Z (8 months ago)
• Language: Jupyter Notebook
• Homepage: https://noklam.github.io/kedro-softfail-runner
• Size: 324 KB
• Stars: 2
• Watchers: 2
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-kedro - kedro-softfail-runner - Custom Kedro Runner to enable soft-failing pipeline. ([Kedro plugins](https://docs.kedro.org/en/stable/extend_kedro/plugins.html))

README

        
# IMPORTANT NOTE: kedro-softfail-runner HAS MOVEVD TO A [NEW HOME](https://github.com/noklam/kedro-runners). THIS REPO IS DEPRECATED.

# kedro-softfail-runner

!!!!! Deprecated, for kedro>0.19 support it is moved to https://github.com/noklam/kedro-runners as a collection of runners

This file will become your README and also the index of your

documentation.

## Install

``` sh

pip install kedro_softfail_runner

```

## How to use

Fill me in please! Don’t forget code examples:

`kedro run --runner=kedro_softfail_runner.SoftFailRunner`

# Why is it useful?

> The team created a soft-fail runner to transform errors into warnings,

> allowing the pipeline to continue executing to the best of its ability

> while providing a report of any nodes that failed, so that data issues

> can be addressed. At that point, the pipeline run can be finalised by

> executing only those missing nodes separately, using appropriate Kedro

> syntax. https://kedro.org/blog/build-a-custom-kedro-runner

It’s most useful in two different scenarios: 1. Development - you want

to detect all problematic nodes in one go 2. Deployment - you want to

run as much node as you can before the Kedro pipeline is stopped.

# Why is it not in Kedro yet?

Note that the

[`SoftFailRunner`](https://noklam.github.io/kedro-softfail-runner/core.html#softfailrunner)

does not return anything, that is `result = session.run()` normally

returns a dictionary of free output, but it will be always `None` for

[`SoftFailRunner`](https://noklam.github.io/kedro-softfail-runner/core.html#softfailrunner)

due to implementation problem.

Other than that, there are no other known issues yet. In order to merge

this into the core library, this problem need to be fixed and the runner

should be test thoroughly.