ray/doc/source/ray-core/actors
Eric Liang 38925f60d2
Add a get_if_exists option for simpler creation of named actors (#23344)
Getting or creating a named actor is a common pattern, however it is somewhat esoteric in how to achieve this. Add a utility function and test that it doesn't cause any scary error messages.

Actor.options(name="my_singleton", get_if_exists=True).remote(args)
2022-03-23 22:02:58 -07:00
..
patterns [docs] Fix malformatted list in "Advanced Pattern: Fault Tolerance with Actor Checkpointing" (#23319) 2022-03-18 10:50:13 -07:00
actor-utils.rst [docs] Core docs refactor (#23216) 2022-03-17 11:26:17 -07:00
async_api.rst [docs] Core docs refactor (#23216) 2022-03-17 11:26:17 -07:00
concurrency_group_api.rst [docs] Core docs refactor (#23216) 2022-03-17 11:26:17 -07:00
fault-tolerance.rst [docs] Core docs refactor (#23216) 2022-03-17 11:26:17 -07:00
named-actors.rst Add a get_if_exists option for simpler creation of named actors (#23344) 2022-03-23 22:02:58 -07:00
scheduling.rst [Doc] Add scheduling doc (#23343) 2022-03-20 16:05:06 -07:00
task-orders.rst [RFC][Doc] add a page describe actor execution order. (#23406) 2022-03-23 11:07:18 -07:00
terminating-actors.rst [docs] Core docs refactor (#23216) 2022-03-17 11:26:17 -07:00