[
https://issues.apache.org/jira/browse/ARROW-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyuan Zhuang updated ARROW-2759:
---------------------------------
Description:
Currently, I am implementing an async interface for Ray. The implementation
needs some kind of message polling methods like `get_next_notification`.
Unfortunately, I find `get_next_notification` in
`[https://github.com/apache/arrow/blob/master/python/pyarrow/_plasma.pyx]`
blocking, which is an impediment to implementing async utilities. Also, it's
hard to check the status of the socket (it could be closed or break up). So I
suggest export the notification socket so that there will be more flexibility.
was:
Currently, I am implementing an async interface for Ray. The implementation
needs some kind of message polling methods like `get_next_notification`.
Unfortunately, I find `get_next_notification` in
`https://github.com/apache/arrow/blob/master/python/pyarrow/_plasma.pyx`
blocking, which is an impediment to implementing async utilities. So I suggest
adding some parameters like `timeout`. It could be done by operating its
underlying socket.
> Export notification socket of Plasma
> ------------------------------------
>
> Key: ARROW-2759
> URL: https://issues.apache.org/jira/browse/ARROW-2759
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Plasma (C++), Python
> Reporter: Siyuan Zhuang
> Priority: Major
>
> Currently, I am implementing an async interface for Ray. The implementation
> needs some kind of message polling methods like `get_next_notification`.
> Unfortunately, I find `get_next_notification` in
> `[https://github.com/apache/arrow/blob/master/python/pyarrow/_plasma.pyx]`
> blocking, which is an impediment to implementing async utilities. Also, it's
> hard to check the status of the socket (it could be closed or break up). So I
> suggest export the notification socket so that there will be more flexibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
