19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
r
Rubén Lopez Lozoya
09/28/2021, 12:50 PMHey team, is there a way to have any sort of solid decorator that always unpacks the received results? I'm upgrading to 0.12 version and I have a lot of pipelines breaking because of that. I see you mentioned in the past that you used namedtuples to return multiple values, but I was wondering if I can do that with a wrapper to avoid having to refactor the whole codebase
I get this all the time and I believe its due to unpacking
E dagster.core.errors.DagsterInvalidDefinitionError: Input "accounts" in solid "solid_remove_duplicate_accounts" is not connected to the output of a previous solid and can not be loaded from configuration, creating an impossible to execute pipeline. Possible solutions are:
E * add a dagster_type_loader for the type "DataFrame"
E * connect "accounts" to the output of another solidThe input accounts is mapped to an output
It only happens after updating Dagster to 0.11.15 (was on 0.11.14 before)
After some debugging I found out that this only happens when I have one composite inside another composite and it happens when I directly pass to a solid the inputs of the composite solid
o
owen
09/28/2021, 4:47 PMhi @Rubén Lopez Lozoya do you have an example pipeline where this is happening?
r
Rubén Lopez Lozoya
09/28/2021, 4:48 PMSure I will PM you