westonpace commented on pull request #11145: URL: https://github.com/apache/arrow/pull/11145#issuecomment-920216234
> I'm going to look at tracing again and would like to do this. It would also be nice if we could get an "async stack trace" of some sorts, perhaps by reconstructing via spans - right now with async, the stack trace in the debugger is essentially useless, unfortunately. If you can solve that it would be awesome. Keep in mind there is a possible another approach. If ExecPlan gets more and more robust then switching the scanner to use ExecPlan internally (so ScanNode becomes ScanDirectoryNode/ScanDatasetNode -> ScanFragmentNode -> ParseBatchNode) is possible and, if we do that, we don't need futures nearly as much and the stack traces should be more sensible (since they'd start with "task" and not "random transferred continuation") -- 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]
