2010YOUY01 commented on issue #19846: URL: https://github.com/apache/datafusion/issues/19846#issuecomment-3768160778
> I suggest we do both > > We definitely shouldn't be `warn`ing for a known issue. This is not a known issue; it is more like an assertion guarding against a potential vulnerability. We do not yet know when or how it fails. If we keep it as a warning, we should first identify the concrete cases that trigger it, open issues for those cases, and only suppress the specific scenarios that are understood and expected. Ideally, we should further investigate the producer side and understand why it can violate the expected memory accounting. Blindly suppressing this warning may hide real problems and could lead to more serious memory bloat issues in the future. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
