travis-cook-sfdc commented on issue #28870:
URL: https://github.com/apache/airflow/issues/28870#issuecomment-1402800228
I'm interesting in potentially implementing this change, but it's not clear
to me exactly what the implementation should look like.
Can anyone provide a summary?
travis-cook-sfdc commented on issue #28870:
URL: https://github.com/apache/airflow/issues/28870#issuecomment-1387745349
> nice discussion. I see the problem now, and yeah, I agree having support
for dynamic collection of links in operator is a better idea
@potiuk - It does seem like
travis-cook-sfdc commented on issue #28870:
URL: https://github.com/apache/airflow/issues/28870#issuecomment-1387738430
After a little more investigation, I think that example only works because
the extra link is registered as a provider which doesn't require explicit
instantiation. If
travis-cook-sfdc commented on issue #28870:
URL: https://github.com/apache/airflow/issues/28870#issuecomment-1387616659
@Taragolis - Interesting example. I thought I had tried something similar,
but I ran into problems when I attempted to register subclass of
`BaseOperatorLink` as an
travis-cook-sfdc commented on issue #28870:
URL: https://github.com/apache/airflow/issues/28870#issuecomment-1386213733
This is different than implementing multiple OperatorLinks for a few reasons:
- The number of links required is unknown at instantiation. It's dependent
on the
