[FEA][JNI] Move to RMM apis get_current_device_resource_ref and set_current_device_resource_ref #16673
Labels
feature request
New feature or request
Java
Affects Java cuDF API.
Spark
Functionality that helps Spark RAPIDS
This change rapidsai/rmm#1661 deprecates the pointer based
get_current_device_resource
andset_current_device_resource
in favor of a non-owning reference basedset_current_device_resource_ref
andget_current_device_resource_ref
.RMM JNI currently uses the pointer based apis so we want to move to the new
_ref
versions. I don't think we need to worry about ownership, because we already have a java object tracking a heap allocated memory resource.The text was updated successfully, but these errors were encountered: