You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, if you use Ray, your entire dag needs to be ray specific. Ideally, we could use Ray and automatically detect when to export the outputs and pass them to a downstream non-ray task.
The text was updated successfully, but these errors were encountered:
Interesting. I am looking at getting data from an external source, say MQTT, to ray tasks and then out to external sources, say MQTT again or a database. Is there a manual way to do it while we wait for the possibly to come automatic one?
Also, I heard of Ray Serve task being in the works - is there a way to use Ray Serve'd tasks at the moment - say substituting the Ray task in the above (MQTT -> Ray Serve -> MQTT). In other words, if the data pulled from MQTT was put in the ray object store by a ray task, then can Ray Serve be called next and would it be able to access the data in the ray object store?
Right now, if you use Ray, your entire dag needs to be ray specific. Ideally, we could use Ray and automatically detect when to export the outputs and pass them to a downstream non-ray task.
The text was updated successfully, but these errors were encountered: