dstandish commented on PR #39046: URL: https://github.com/apache/airflow/pull/39046#issuecomment-2070243292
> I hear what you're saying about TI Tries, however, I don't think that's a good/valid argument to not do the best we can to maintain the correct state for the latest try, just because we don't have data for any previous tries. I see no reason to allow clobbering the latest TI try, with the latest parsed task. I see no reason why we can't try to do incrementally better about confusing user experiences with regards to entities mutating at runtime, just because there is an existing precedent. I agree. If you can "not clobber the history" while still allowing the current config to be respected at runtime, you have my support :). I don't _think_ that's what the PR was doing... but maybe I misunderstood. -- 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]
