i wasn’t able to find anything about this in the user guide, but am i allowed to do blocking operations inside an :fn transformation ? i.e. doing HTTP requests and awaiting the results

i feel that it will have a huge impact on performance if not done async

so i’m looking for a best practice here

solutions that i can come up with is splitting this out into two different tasks, and using core.async (= very ugly), or creating a window function (= also very ugly) was hoping there would be native support to return a core.async channel or promise or something from the :fn function

guess that would have a lot of consequences for flow control tho

@lmergen you could mark your :fn as a batch fn http://www.onyxplatform.org/docs/cheat-sheet/latest/#catalog-entry/:onyx/batch-fn-QMARK which would allow you to run a bunch of async tasks concurrently, improving your throughput

d’oh, of course, you’re completely right this would solve my problem

thanks!

much more simple this way

@mccraigmccraig Yep. 🙂