Channels
dagster-de
integration-airbyte
topic-async-execution
local-japan
dagster-cube
community-freelance
dagster-wandb
dagster-feedback
community-machine-learning
integration-bigquery
dagster-university
ask-community
dagster-dask
integration-snowflake
dagster-releases
integration-dbt
faq-read-me-before-posting
tools
feature-insights
feature-pipes
project-flexible-range-backfills
data-platform-design
community-events
dagster-serverless
dagster-noteable
introductions
integration-airflow
dagster-cloud
random
dagster-spatial
ask-ai
announcements
github-discussions
豆瓣酱帮
dagstereo
deployment-ecs
deployment-kubernetes
jobs
community-showcase
feature-asset-checks
Powered by
#dagster-feedback
Title
# dagster-feedback
b
Binoy Shah
08/16/2022, 8:13 PM
One thing I am a bit hazy about is what is the “contractual obligation” of the function annotated with either
@op
or
@asset
, what is it supposed to be returning such that the
op
/
asset
decorator can parse the returned objects correctly ?
🤖 1
s
sandy
08/16/2022, 10:38 PM
hey
@Binoy Shah
- we've tried to document this here:
https://docs.dagster.io/concepts/ops-jobs-graphs/ops#outputs
let us know if there are ambiguities there
b
Binoy Shah
08/16/2022, 10:42 PM
Oh okay, I have been confusing myself with Dagster being able to “understand” the output, I carried impression that Dagster knows about the data and data entries within the output result
Post