You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/05/17 23:45:27 UTC

[GitHub] [arrow] westonpace commented on pull request #10118: ARROW-12468: [Python][R] Expose ScannerBuilder::UseAsync to Python & R

westonpace commented on pull request #10118:
URL: https://github.com/apache/arrow/pull/10118#issuecomment-842715892


   > Elsewhere, we use a global option for governing e.g. whether to use multithreading, would that be appropriate here?
   
   A global option seems like it should be fine.
   
   > Do you expect this to always be optional, or is it only optional for now while you sort out the performance optimization?
   
   I expect it should go away at some point.  Either we get to the point where the overhead is negligible or the filesystems themselves could determine what kind of mode to use (potentially via io context).


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

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