[GitHub] [arrow-cookbook] ianmcook opened a new issue, #212: [R] Refer to the Arrow C++ compute engine as **Acero**

[GitBox <gi...@apache.org>]

ianmcook opened a new issue, #212:
URL: https://github.com/apache/arrow-cookbook/issues/212

   Once [ARROW-16632](https://issues.apache.org/jira/browse/ARROW-16632) and [ARROW-16626](https://issues.apache.org/jira/browse/ARROW-16626) are complete, we should update some of the text in the R cookbook to refer to the Arrow C++ compute engine using its new name, **Acero**. We should try to be quite explicit about the fact that the {arrow} R package converts {dplyr} code into an Acero ExecPlan.


-- 
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-cookbook] thisisnic commented on issue #212: [R] Refer to the Arrow C++ compute engine as Acero

[GitBox <gi...@apache.org>]

thisisnic commented on issue #212:
URL: https://github.com/apache/arrow-cookbook/issues/212#issuecomment-1136164762

   Happy to update "Arrow C++ compute engine to Acero" but can you expand upon where
   
   > We should try to be quite explicit about the fact that the {arrow} R package converts {dplyr} code into an Acero ExecPlan.
   
   would fit, in terms of where in the cookbook it'd be relevant to mention this?  I'm not entirely convinced that this is the right place to be talking about ExecPlans as it feels like a fairly technical level of detail that belongs in other documentation (though open to being persuaded otherwise!)


-- 
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-cookbook] ianmcook commented on issue #212: [R] Refer to the Arrow C++ compute engine as Acero

[GitBox <gi...@apache.org>]

ianmcook commented on issue #212:
URL: https://github.com/apache/arrow-cookbook/issues/212#issuecomment-1140321525

   > can you expand upon where
   > 
   > > We should try to be quite explicit about the fact that the {arrow} R package converts {dplyr} code into an Acero ExecPlan.
   > 
   > would fit, in terms of where in the cookbook it'd be relevant to mention this?
   
   Yes, I think it would be valuable to add some content about this to the [Manipulating Data - Tables](https://arrow.apache.org/cookbook/r/manipulating-data---tables.html) R cookbook entry. It would be great if that cookbook entry could explain what happens under the hood when the user calls dplyr verbs on an Arrow table/recordbatch/dataset and then calls `collect()` or `compute()`: an Acero ExecPlan is constructed and executed.


-- 
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-cookbook] thisisnic commented on issue #212: [R] Refer to the Arrow C++ compute engine as Acero

[GitBox <gi...@apache.org>]

thisisnic commented on issue #212:
URL: https://github.com/apache/arrow-cookbook/issues/212#issuecomment-1141025196

   OK, make sense, we could mention that briefly in the intro and then link to some docs where it's explained in more detail.  


-- 
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