zhengruifeng commented on PR #49005: URL: https://github.com/apache/spark/pull/49005#issuecomment-3283499742
> Gentle ping again, it's getting tricky to keep up with/figure out new merge conflicts each time there are conflicting changes that make it in @Kimahriman we plan to optimize the batch size in multiple python plans (e.g. SQL_GROUPED_MAP_PANDAS_UDF /SQL_GROUPED_MAP_ARROW_UDF /SQL_GROUPED_AGG_ARROW_UDF/SQL_GROUPED_AGG_PANDAS_UDF/SQL_WINDOW_AGG_PANDAS_UDF/SQL_WINDOW_AGG_ARROW_UDF/etc), [this](https://github.com/apache/spark/pull/52303) is the first one for SQL_GROUPED_MAP_PANDAS_UDF /SQL_GROUPED_MAP_ARROW_UDF. Can the iterator API reuse this change? Regarding this PR, I think we should: 1, exclude any changes in cogroup; 2, add a new eval type for the new iterator API, because it is a user-facing change. For example, we have `SQL_SCALAR_PANDAS_ITER_UDF` for the iterator API in Pandas UDF. -- 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: reviews-unsubscr...@spark.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
