icexelloss opened a new issue, #37919: URL: https://github.com/apache/arrow/issues/37919
### Describe the enhancement requested Currently, most of the aggregation kernels have destructive finalize call, that is, the kernel state is invalid after finalize is called. This by itself, is not a problem, because non of the existing compute/acero code tries to use a kernel state after finalize call. However, recently, I am trying to reuse the aggregation kernels to implement some accumulative behavior, i.e., accumulate inputs into the kernel until some conditions are met, call finalize to get the aggregation output, then keep adding data to it. (e.g., scan a year of data and output the accumulative mean every day). The destructive finalize call stops me from doing sth like this. Based on this use case, I propose to have an option to allow aggregation kernels to have non destructive finalize call, so that the user of the kernels can use them in an accumulative way. Thoughts? ### Component(s) C++ -- 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]
