pierrejeambrun commented on PR #42410: URL: https://github.com/apache/airflow/pull/42410#issuecomment-2462379944
Those are just unreasonable values and it is not a surprise to me that things break down the line. If I code a mapped task that expand to (2*32 - 1) most likely things will also break. We can always add a safeguard, or a better error handling on the scheduler side to make that more explicit, but changing the underlying datatype to allow usage of extremely high values does not achieve much (IMO). Also I believe that this could be enforced by a custom cluster policy if developers tend to put unreasonable values here and it becomes a problem for a company. -- 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]
