zeroshade commented on PR #40807: URL: https://github.com/apache/arrow/pull/40807#issuecomment-2079653168
> When exported over the C Data interface it is a requirement, no? (Or at least, a better option than exporting a device array that is potentially yet synchronized with a nullptr sync event?) Yea, the sync event is at the top level of the ArrowDeviceArray struct to represent that the data for a single ArrowArray should always be tied to a single sync event, or have no synchronization required. Thus any joining / handling of multiple sync events needs to be managed by the producer so it can generate a *single* sync event if synchronization is needed. As such, this code will use that sync event when constructing imported record batches so that the event can be propagated. But once you are manually constructing record batches from existing Arrow Arrays, all bets are off, which is why we just take a sync event as an argument when constructing the record batches. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
