yjshen commented on pull request #811:
URL: https://github.com/apache/arrow-datafusion/pull/811#issuecomment-902533289


   @alamb 
   
   > The alternate compromise, which you have partly implemented in this PR, is 
to implement both async and non async versions. This is similar to the approach 
in the C/C++ filesystem api (props to @nealrichardson for the pointer), which 
has both having synchronous and asynchronous APIs.
   
   If I understand you correctly, do you mean I should tell sync and async 
implementation apart, with two different logics? Instead of the current wrapper 
way (sync function wrap over async logic.)


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

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


Reply via email to