Taepper commented on issue #47642: URL: https://github.com/apache/arrow/issues/47642#issuecomment-4592069524
Ah, great that this was resolved in such a simple fashion! I initially thought that this could also be solvable by tweaking the destructor's in a way such that they clean up / decrement `running_tasks_` appropriately and the stack unwind of the exception will already be enough to circumvent the "never finishing Acero plan". But an explicit `try ... catch` is of course also viable. Note that a `bad_alloc` can also trigger this hang, which can be thrown by the standard library. So to guard against this in user code as briefly suggested in #49860, would essentially require compiling with `-fno-exceptions` in any project using acero -- 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]
