You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by "doki23 (via GitHub)" <gi...@apache.org> on 2023/06/14 01:07:33 UTC

[GitHub] [arrow-datafusion] doki23 commented on pull request #6617: RFC: User Defined Window Functions

doki23 commented on PR #6617:
URL: https://github.com/apache/arrow-datafusion/pull/6617#issuecomment-1590276664

   > Hence I think, we should either support for user to create custom BuiltInWindowFunctionExpr for each new WindowUDF (I think this is hard and more cumbersome on the user side) or we should move all the parameters that effects the decision (such as supports_bounded_execution, uses_window_frame, include_rank) to the evaluator and/or aggregator side. By this way user will have full control on the custom implementation.
   
   How about moving `supports_bounded_execution` and `uses_window_frame` into the evaluator?


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org