njnu-seafish commented on PR #17856: URL: https://github.com/apache/dolphinscheduler/pull/17856#issuecomment-3721532700
> Task results can be treated as part of the task execution context, but this should only store elements like the task result path. It is not suitable for storing SQL output. We should not store task outputs or similar content in the database, as this is highly non-generic, the output might very large. To prevent excessive resource usage, the size of task result alerts must be constrained—just as we do with log output by limiting the number of displayed lines. > For such alerts, we do not need to persist them to the database. Alert sending should be asynchronous to avoid blocking the main flow. Without persistence, alerts could be lost—currently, all alerts are stored in the DB first, and the Alert service processes them from there. -- 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]
