shivaam commented on issue #69288:
URL: https://github.com/apache/airflow/issues/69288#issuecomment-5120907975
Okay, I think it makes sense to keep a single authoring interface and remove
`registerTask()`.
I want to clarify how the existing Python-Dag/TypeScript-handler mode would
work. In that mode, Python defines the complete Dag, while TypeScript only
provides the implementation for one or more tasks.
If the TypeScript user creates a `new Dag()` with the same `dagId` and adds
those handlers, it would only be a partial representation. Python would still
own the schedule, dependencies, and remaining tasks.
Normally, `registerDags()` would tell the coordinator to serialize the
TypeScript Dag as a complete Dag. Doing that here could create a second,
incomplete definition with the same `dagId`.
How should the coordinator know that this TypeScript object is only
registering handlers and should not be serialized? Would `Dag` need an explicit
handler-only/external mode, or would this association happen through another
mechanism?
Something like:
```
new Dag({
dagId: "sales_pipeline",
mode: "handlerOnly",
});
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
