carols10cents opened a new pull request, #15030: URL: https://github.com/apache/datafusion/pull/15030
To start a policy of the behavior physical operator streams should have and drive improvements in this area to allow for timely cancellation. I'm very open to any wording changes and looking forward to discussion on whether I've accurately captured the intent of datafusion! ## Which issue does this PR close? Connects to #14036 and related to pull requests such as #14028. ## Rationale for this change Datafusion should be explicit about its aspirations for what it provides as well as provide guidelines for trait implementers about yielding to enable timely cancellation. ## What changes are included in this PR? A policy statement in the documentation with some reference links. ## Are these changes tested? No, this is only documentation. ## Are there any user-facing changes? This is the documentation :) -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
