arthur-ventura-astro commented on PR #51056: URL: https://github.com/apache/airflow/pull/51056#issuecomment-2927441916
> Overall looks good. I still think this is more a temporary solution than a production-grade solution. Relying on variables and the fact that the user will update this variable to the latest timestamp will not work on the long run. We should definitely invest on implementing a robust solution to share a state among triggers. This is actually a super interesting topic, if anybody has some bandwith :) If someone is interested, I'll be happy to help. > > Action item for this PR: can you please create docs? Explaining the trigger, giving some real world example and mentioning that the variable must be updated. @jose-lehmkuhl nice PR! I was about to submit one myself on the same topic. I've opened a [draft](https://github.com/apache/airflow/pull/51254l) with a few different approaches that could be complementary to this subject. I'm happy to help moving this forward, not only for Postgres but also for other SQL providers. One roadblock we have to face is using synchronous connections to achieve this. Although not ideal, a bottom limit for the `poke_interval` in that case might help for now. For the long-term solution maybe we can make it work with [asyncpg](https://github.com/MagicStack/asyncpg). -- 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]
