Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to mix ray vs other operators #24

Open
richardliaw opened this issue May 18, 2021 · 1 comment
Open

Ability to mix ray vs other operators #24

richardliaw opened this issue May 18, 2021 · 1 comment

Comments

@richardliaw
Copy link
Collaborator

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.

@mkiruja-adapdix
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants