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

[GitHub] [arrow] kkraus14 commented on pull request #34972: GH-34971: [Format] Enhance C-Data API to support non-cpu cases

kkraus14 commented on PR #34972:
URL: https://github.com/apache/arrow/pull/34972#issuecomment-1504195071

   @pitrou I think the other thing that hasn't been discussed in the above threads with regards to producer vs consumer provided stream is the development burden that will have to be incurred by the consumer in the different situations.
   
   In producer provided stream / event:
   - The default behavior would be for the producer to return a stream or event in the struct if appropriate based on the producer
   - It forces the consumer to understand and handle device streams / events, which could be a non-trivial ask
   - There's no way for the consumer to ask for the data to be synchronized and safe to access from any stream and for the stream or event to be nullptr
   
   In consumer provided stream:
   - The default behavior would be the consumer not providing a stream which would inform the producer to guarantee the data to be synchronized and safe to access from any stream
   - Someone could use consumer code that doesn't understand or utilize device streams or events in any way without issue


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