hussein-awala commented on PR #70225: URL: https://github.com/apache/airflow/pull/70225#issuecomment-6451666116
Thanks for the changes. I prefer option 3. `RunStart(lookback=...)` makes the common case clear. A callable can cover custom bounds. The bound objects could use the same callable interface, with one path to resolve after and before. For the first version, I suggest these requirements: - Keep support for datetime values and ISO strings. - Define the behavior when the selected context value is missing. - Keep the bounds fixed while the sensor polls. - Test serialization and mapped tasks. The built-in bounds also need a defined serialized form to support non-Python SDKs. I agree that tracking the last consumed event belongs in a separate issue. That feature needs persistent state and clear rules for retries and concurrent runs. -- 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]
