Context
From TP's comment:
I feel we should proably not subclass a DagBundle… Subclassing Dag feels more natural. This is something I want to review before the SDK hits 1.0.
Why I proposed DagBundle in the first place:
The design of DagBundle here is only the for getDags interface to expose the DagId and TaskIds metadata in the build time.
What
If we want to avoid the DagBundle subclass here, it possible to achieve it by sending the DagParsingRequest and parse the serialized dag json to get the metadata in the build time.
Context
From TP's comment:
Why I proposed
DagBundlein the first place:What
If we want to avoid the
DagBundlesubclass here, it possible to achieve it by sending theDagParsingRequestand parse the serialized dag json to get the metadata in the build time.