[Client] Provide common ObjectRefType
See original GitHub issueDescribe your feature request
We do a lot of defensive type checking in Modin when using Ray to make sure that things are working. It would be very convenient if ClientObjectRef
extended ObjectRef
so that assertions like assert(isinstance(obj, ray.ObjectRef))
would still work without needing to handle the Client object separately.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Modin fails to load csv from s3 with ray client #2688 - GitHub
Modin fails to load csv from s3 with ray client #2688 ... [Client] Provide common ObjectRefType ray-project/ray#14042.
Read more >OVAL VMware ESX server Definition Schema Element ...
Each test is described in detail and should provide the information ... The common set element allows complex objects to be created using ......
Read more >rim.xsd
A list of ObjectRefType instances. This type is the common base type for all query-able metadata elements in ebRIM. A List of IdentifiableType...
Read more >Open Vulnerability and Assessment Language: Solaris Definition ...
Each test is described in detail and should provide the information ... The common set element allows complex objects to be created using...
Read more >Standards Writing Template for .dot users - OGC Portal
[11] National Center for Supercomputing Applications, "The Common Gateway ... BBOXPROPERTY parameter is included to allow the client to indicate the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Would it be possible to only have a single
ObjectRef
type for both client and the rest of Ray? Certainly from the API side that would be the simplest (no need foris_object_ref_type
etc)?If the implementation requires it, the
ObjectRef
could have an internal distinction if it is a client ref or a Ray ref.Sounds good @ericl, we’ll do that.