You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "andygrove (via GitHub)" <gi...@apache.org> on 2023/02/25 00:04:07 UTC

[GitHub] [arrow-ballista] andygrove opened a new issue, #684: Support executing query stages in execution engines other than DataFusion

andygrove opened a new issue, #684:
URL: https://github.com/apache/arrow-ballista/issues/684

   **Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
   When the executor receives a task, it deserializes the physical plan, wraps it in a `ShuffleWriterExec`, and executes it with DataFusion.
   
   I want the ability to override this behavior to execute the plan in execution engines other than DataFusion.
   
   **Describe the solution you'd like**
   In the executor, we call `new_shuffle_writer` to create the `ShuffleWriterExec` that wraps the plan to be executed. I am thinking about moving that method into a new `ExecuionEngine` trait and creating a `DataFusionExecutor` implementation of the trait that is used by default.
   
   We can then add a field to `ExecutorProcessConfig` as follows:
   
   ```rust
   execution_engine: Option<Arc<dyn ExecutionEngine>>
   ```
   
   This will allow me to register custom execution engines from PyBallista, and execute distributed queries in Polars, Pandas, and cuDF.
   
   **Describe alternatives you've considered**
   None
   
   **Additional context**
   None
   


-- 
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-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [arrow-ballista] mingmwang commented on issue #684: Support executing query stages in execution engines other than DataFusion

Posted by "mingmwang (via GitHub)" <gi...@apache.org>.
mingmwang commented on issue #684:
URL: https://github.com/apache/arrow-ballista/issues/684#issuecomment-1552318718

   @andygrove 
   I like this idea. For the other execution engines, do you have any proposal ?


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Support executing query stages in execution engines other than DataFusion [arrow-ballista]

Posted by "andygrove (via GitHub)" <gi...@apache.org>.
andygrove commented on issue #684:
URL: https://github.com/apache/arrow-ballista/issues/684#issuecomment-1894034053

   I am closing this for now because I think it is too ambitious given the current level of development in the project. 


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [arrow-ballista] jdye64 commented on issue #684: Support executing query stages in execution engines other than DataFusion

Posted by "jdye64 (via GitHub)" <gi...@apache.org>.
jdye64 commented on issue #684:
URL: https://github.com/apache/arrow-ballista/issues/684#issuecomment-1444772044

   I have been thinking about this a lot today. I have had numerous ideas and all seem to have fell flat as I tried to fully implement them. I like the general idea however and curious to see how it looks fully materialized. Interesting stuff for sure!


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [arrow-ballista] andygrove commented on issue #684: Support executing query stages in execution engines other than DataFusion

Posted by "andygrove (via GitHub)" <gi...@apache.org>.
andygrove commented on issue #684:
URL: https://github.com/apache/arrow-ballista/issues/684#issuecomment-1444767539

   @Dandandan @thinkharderdev @yahoNanJing @avantgardnerio @jdye64 fyi - let me know if you have any opinions on this approach. I am going to build a prototype of this over the next week. I am sure the design will evolve as I try and implement this.


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [arrow-ballista] andygrove commented on issue #684: Support executing query stages in execution engines other than DataFusion

Posted by "andygrove (via GitHub)" <gi...@apache.org>.
andygrove commented on issue #684:
URL: https://github.com/apache/arrow-ballista/issues/684#issuecomment-1444817016

   There needs to be a scheduler element to this as well so we can do the plan translation once rather than per task.


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Support executing query stages in execution engines other than DataFusion [arrow-ballista]

Posted by "andygrove (via GitHub)" <gi...@apache.org>.
andygrove closed issue #684: Support executing query stages in execution engines other than DataFusion
URL: https://github.com/apache/arrow-ballista/issues/684


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org