berkaysynnada merged PR #16892:
URL: https://github.com/apache/datafusion/pull/16892
--
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...@
berkaysynnada commented on PR #16892:
URL: https://github.com/apache/datafusion/pull/16892#issuecomment-3125673259
We don't want to risk discovering a feature breakage later in downstream
projects but let's merge this now. Once I'm able to reproduce the case, I'll
open a follow-up PR with t
alamb commented on PR #16892:
URL: https://github.com/apache/datafusion/pull/16892#issuecomment-3124296290
> is it okay to be merged or we waiting for the test ?
It is ok in my opinion, but let's wait to see if @berkaysynnada has any
thoughts
--
This is an automated message from t
comphead commented on PR #16892:
URL: https://github.com/apache/datafusion/pull/16892#issuecomment-3122166929
is it okay to be merged or we waiting for the test ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
berkaysynnada commented on PR #16892:
URL: https://github.com/apache/datafusion/pull/16892#issuecomment-3113756580
I'll add a test if I can reproduce a failing case
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
berkaysynnada opened a new pull request, #16892:
URL: https://github.com/apache/datafusion/pull/16892
## Which issue does this PR close?
- Closes #.
## Rationale for this change
In some of our use cases, `OutputRequirementExec` requires fetch capability
d