Re: [PR] Blog post on query cancellation [datafusion-site]

2025-07-05 Thread via GitHub
kevinjqliu commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3039741826 Just read the post. Coming back here to thank everyone for the contribution! I always learn so much from these. I think it would be great to have a comment section for the b

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-30 Thread via GitHub
comphead commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3020819996 > The blog is live! https://datafusion.apache.org/blog/2025/06/30/cancellation/ Published on Datafusion Linkedin resource -- This is an automated message from the Apache Git

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-30 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3018782433 The blog is live! https://datafusion.apache.org/blog/2025/06/30/cancellation/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-30 Thread via GitHub
alamb commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2174839499 ## content/blog/2025-06-30-cancellation.md: ## @@ -0,0 +1,490 @@ +--- +layout: post +title: Using Rust async for Execution and Cancelling Long-Running Queries Review

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-30 Thread via GitHub
alamb merged PR #75: URL: https://github.com/apache/datafusion-site/pull/75 -- 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: github-unsubscr...@datafusio

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-25 Thread via GitHub
pepijnve commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3003597592 > https://without.boats/blog/asynchronous-clean-up/ Wait till you read their work on Pin/Unpin. -- This is an automated message from the Apache Git Service. To respond to the

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-25 Thread via GitHub
pepijnve commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3005104426 @alamb I've done some work to make the diagrams a bit prettier using Excalidraw. Massaged the text a bit further. Tried to improve the flow from one section to the next. -- This i

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-25 Thread via GitHub
pepijnve commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3003623249 > In my opinion this article does a pretty good job explaining the issues with cancellation, but it doesn't talk about `async` destructors which I agree are probably best left out of

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-25 Thread via GitHub
pepijnve commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3003611703 > I was wondering if it makes sense to add challenges why async is challenging to cancel on low level but it probably would be noisy. But just in case this article shed the light on

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-24 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3001676393 In my opinion this article does a pretty good job explaining the issues with cancellation, but it doesn't talk about `async` destructors which I agree are probably best left out of scop

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-24 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3001672876 > I was wondering if it makes sense to add challenges why async is challenging to cancel on low level but it probably would be noisy. But just in case this article shed the light on can

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-24 Thread via GitHub
comphead commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3001443602 I was wondering if it makes sense to add challenges why async is challenging to cancel on low level but it probably would be noisy. But just in case this article shed the light on ca

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-24 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-3000831078 I pushed the images to this post, updated the publish date to June 30 (next Monday), and started doing some wordsmiting ![Screenshot 2025-06-24 at 10 52 01  AM](https://github.com

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-23 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2997787662 > I was not planning on changing it substantially anymore. I was thinking of maybe rereading the text with a fresh pair of eyes and editing a sentence here or there, but that's it. Need

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-23 Thread via GitHub
pepijnve commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2996933820 I was not planning on changing it substantially anymore. I was thinking of maybe rereading the text with a fresh pair of eyes and editing a sentence here or there, but that's it. Nee

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-23 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2996826099 Hi @pepijnve -- I wonder if you plan to work on this post in the near term? If not I will try and find time to add some diagrams / etc to help it get ready to publish (as I think it is

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-20 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2991169813 @pepijnve I pushed an Acknowedgement and "About DataFusion" sections ![Screenshot 2025-06-20 at 7 41 54  AM](https://github.com/user-attachments/assets/f9a880b2-cc56-4bf8-ae12-aca

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-20 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2991145431 > One other thing I'm curious about. This write-up discusses the change in terms of enabling long-running tasks to be cancelled, but would making CPU-intensive exec blocks more cooperat

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
alamb commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2153183826 ## content/blog/2025-06-15-cancellation.md: ## @@ -0,0 +1,353 @@ +--- Review Comment: Yes of course -- we have done this on other blogs as well Something

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
pepijnve commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2152981299 ## content/blog/2025-06-15-cancellation.md: ## @@ -0,0 +1,353 @@ +--- Review Comment: Since Datadobi is paying for my time while I work on this stuff, would it

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
pepijnve commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2152978616 ## content/blog/2025-06-15-cancellation.md: ## @@ -0,0 +1,353 @@ +--- +layout: post +title: Query Cancellation +date: 2025-06-27 +author: Pepijn Van Eeckhoudt +cat

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
pepijnve commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2152976180 ## content/blog/2025-06-15-cancellation.md: ## @@ -0,0 +1,353 @@ +--- +layout: post +title: Query Cancellation +date: 2025-06-27 +author: Pepijn Van Eeckhoudt +cat

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
djanderson commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2152791907 ## content/blog/2025-06-15-cancellation.md: ## @@ -0,0 +1,328 @@ +# Query Cancellation + +## The Challenge of Cancelling Long-Running Queries + +Have you ever tr

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
alamb commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2152732436 ## content/blog/2025-06-15-cancellation.md: ## @@ -0,0 +1,353 @@ +--- Review Comment: I took the liberty of pushing this "front matter" and ASF header to this po

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2981079329 > A colleague of mine suggested to add some more diagrams. I know UML is out of fashion, but here's a sketch of what's actually happening when you imagine Tokio's budget is initiali

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
alamb commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2981082556 FYI @ozankabak and @zhuqi-lucas -- 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 speci

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
pepijnve commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2980346829 A colleague of mine suggested to add some more diagrams. I know UML is out of fashion, but here's a sketch of what's actually happening when you imagine Tokio's budget is initialized

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
pepijnve commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2980078702 > but would making CPU-intensive exec blocks more cooperative also help alleviate blocking IO on the main runtime if users don't set up a separate runtime It should make some

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-17 Thread via GitHub
pepijnve commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2152065111 ## content/blog/2025-06-15-cancellation.md: ## @@ -0,0 +1,328 @@ +# Query Cancellation + +## The Challenge of Cancelling Long-Running Queries + +Have you ever trie

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-16 Thread via GitHub
djanderson commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2978267914 One other thing I'm curious about. This write-up discusses the change in terms of enabling long-running tasks to be cancelled, but would making CPU-intensive exec blocks more coop

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-16 Thread via GitHub
djanderson commented on code in PR #75: URL: https://github.com/apache/datafusion-site/pull/75#discussion_r2150859260 ## content/blog/2025-06-15-cancellation.md: ## @@ -0,0 +1,328 @@ +# Query Cancellation + +## The Challenge of Cancelling Long-Running Queries + +Have you ever tr

Re: [PR] Blog post on query cancellation [datafusion-site]

2025-06-15 Thread via GitHub
pepijnve commented on PR #75: URL: https://github.com/apache/datafusion-site/pull/75#issuecomment-2974061097 I've marked this as draft for now. I think I have the narrative arc I was going for in place, but the text probably still needs some editing work. -- This is an automated message f

[PR] Blog post on query cancellation [datafusion-site]

2025-06-15 Thread via GitHub
pepijnve opened a new pull request, #75: URL: https://github.com/apache/datafusion-site/pull/75 (no comment) -- 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,