Quick question from my side; what’s the added benefit of implementing this pattern? Is the main value prop that DAGs can be defined in new ways and parsed with a specific interface? Because Airflow already supports parsing YAML files with dag-factory, and things like JSON with homegrown DAG generators. Is there a performance component?
On Jun 5, 2026 at 7:43:11 AM, Jarek Potiuk <[email protected]> wrote: > Generally lack of comments or even 'looks good' means that no-one had time > to look at it - and not that they have no objections. No objections > assumption is reserved for LAZY CONSENSUS when consensus seems to be > achieved > > On Fri, Jun 5, 2026, 13:40 Jarek Potiuk <[email protected]> wrote: > > To be honest - I do not think there was enough of a discussion on it to > > start vote thread. And certainly not recently. No-one had any comments on > > it after scoping down and placing it in Confluence > > > J. > > > On Fri, Jun 5, 2026, 13:23 Dilnaz Amanzholova via dev < > > [email protected]> wrote: > > > > Hi all, > > > > > > I’m calling vote on AIP-85: DAG importer > > > https://cwiki.apache.org/confluence/x/_Q7OEg > > > > > > You can also review the design document here > > > < > > > > https://docs.google.com/document/d/1K6-4cGoZItXGQHZjOydNbc7rGtOp_XKfFurMnFptKe0/edit?tab=t.0 > > > > > > > . > > > > > > Current discussion thread (after scoping down): > > > https://lists.apache.org/thread/wtfog0qjrf3oh7355db0x6mqk3o7l2dt > > > Original discussion thread (with wider "extendable DAG parsing controls" > > > title): https://lists.apache.org/thread/bn0oo47j48xh8r335gd2jrrjz0o7vnjl > > > > > > The vote will run for 5 days, closing on Wednesday, 10th June 2026, at > > > 10:00 UTC. > > > > > > Everyone is encouraged to vote, but only PMC members and Committers' > votes > > > are considered binding. Please vote accordingly. > > > > > > [ ] +1 Approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > Kind regards, > > > Dilnaz Amanzholova > > > > > >
