The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hey all, I'm having an issue with using op factories. I'm getting an error `Detected conflicting node definitions with the same name` when generating two ops using <https://docs.dagster.io/integrations/databricks#step-2-create-an-opasset-that-connects-to-databricks|the Databricks op factories>. Could you tell me what I'm doing wrong? Code in thread

```databricks_job_id = 12

my_databricks_run_now_op = create_databricks_run_now_op(
    databricks_job_id = databricks_job_id,
    databricks_job_configuration={
        "spark_submit_params": '1'
    }
)

my_databricks_run_now_op2 = create_databricks_run_now_op(
    databricks_job_id = databricks_job_id,
    databricks_job_configuration={
        "spark_submit_params": '2'
    }
)

@graph_asset
def databricks_asset():
    return my_databricks_run_now_op()

@graph_asset
def databricks_asset_2():
    return my_databricks_run_now_op2()```

Hi Neil--this is a bug. This is cause by the `create_databricks_run_now_op` function which always returns an op named `_databricks_run_now_op` , which is why you're getting the conflicting definitions error.

I think we need to make the function accept a `name` param which can be passed into the op definition to make the ops unique.

I have a PR out for this: <https://github.com/dagster-io/dagster/pull/13629>

Thanks, Claire! Really appreciate the quick turnaround