Daggy Alternatives

Similar projects and alternatives to daggy

materialize

117 5,558 10.0 Rust daggy VS materialize

The data warehouse for operational workloads. (by MaterializeInc)
dbt-expectations

10 932 6.7 Shell daggy VS dbt-expectations

Port(ish) of Great Expectations to dbt test macros
WorkOS

workos.com
sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Scio

7 2,521 9.6 Scala daggy VS Scio

A Scala API for Apache Beam and Google Cloud Dataflow.
cuetils

2 76 0.0 Go daggy VS cuetils

CLI and library for diff, patch, and ETL operations on CUE, JSON, and Yaml
NVTabular

1 1,002 5.5 Python daggy VS NVTabular

NVTabular is a feature engineering and preprocessing library for tabular data designed to quickly and easily manipulate terabyte scale datasets used to train deep learning based recommender systems.
InfluxDB

www.influxdata.com
sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better daggy alternative or higher similarity.

Suggest an alternative to daggy

daggy reviews and mentions

Posts with mentions or reviews of daggy. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-10-08.

ETL Pipelines with Airflow: The Good, the Bad and the Ugly
7 projects | news.ycombinator.com | 8 Oct 2021

Thanks for the feedback. I'll take a look at how Luigi models task state. Right now each TaskExecutor type is responsible for running and reporting on tasks (e.g. the Slurm executor submits jobs and monitors them for completion). I was considering adding a companion "verify" stage for every vertex, which would be a command that ran and verified output. It might be a way to do what I think you're describing above without having to build in a variety of expected outputs into the daggy core. I'll check what Luigi is doing, though.
> resuming a partially failed build
Daggy does this! Right now it will continue running the DAG until every path is completed or all vertices in a processing state (queued, running, retry, error) are in the error state, then the DAG goes to an error state.
It's possible to explicitly set task/vertex states (e.g. mark it complete if the step was manually completed), then change the DAG state to QUEUED, at which point the DAG will resume execution from where it left off. [1] is a unit test that walks through that functionality.
[1] https://gitlab.com/iroddis/daggy/-/blob/master/tests/unit_se...