Registering and Using a Function
Register a function and then use it
Making a function available to HeavyDB--registering-–is based on decorating a Python function. Consider the following simple function, which takes a single argument and return a single value.
Register this function to HeavyDB using the following steps:
Declare the function’s signature.
Attach the signature to the function.
Register the function to the database.
Declaring the Signature
Annotate the function with type information to tell RBC how to translate the function into this intermediate representation, using the following syntax:
The function can only return a single element.
Available types are similar to C types:
In the types listed, items in brackets indicate options to choose from. For example, [List,Array]Int[8,16]
is expanded to mean ListInt8
, ArrayInt8
, ListInt16
, and ArrayInt16
. The literals float
and int
can be abbreviated by f
and i
, respectively.
Returning to the function, if you want both the input argument and the output values as doubles, you could write:
Templating
What happens when the input is an integer? RBC does not cast input values to the expected types automatically. If you expect multiple input types, RBC supports templating (as in C++ or generic in Rust or Go). Templating allows you to define a type using a variable, like T
in this example:
In this example, T
can be replaced by int32
or double
. This can also be written without using a variable.
You can also have different template variables. The Cartesian product is observed.
Attaching the Signature
Once you have the signature, you can attach it to the function. As a best practice, use the signature as a decorator.
This prevents classical function calls of the decorated function. The function is now “marked” to be registered on the server and used there.
Overloading
RBC supports overloading function definitions. This permits several function implementations using a common identifier, with the execution path determined by specific inputs.
Arrays
Both inputs and output can be marked as 1D-arrays or lists of any type. To indicate an array in the function signature, append brackets ([]
) to the type literal.
You can also define an array use the 'Array<double>'
syntax.
Some functions with array support are provided. In this example, the imported function rbc.stdlib.array_api.mean
computes the mean over an array of inputs f_array
. We can also have output arrays.
rbc.stdlib.array_api.mean
is a special function bundled with RBC. In this case, numpy.mean
has been overridden for convenience to users familiar with NumPy’s API. See here for more details and information about supported functions.
To create an array within a function, the class Array
must be used to define an empty array. It can then be indexed to be filled. Slicing or complex indexing is not currently supported. If the array is returned, it’s important that the type specified during the array creation matches the return type specified in the function signature.
Standard Python constructors like list
, dict
or numpy.array
cannot be used to construct arrays supported by RBC. See here for a complete list of array creation functions.
Selecting a Device
You can select explicitly the device on which a function is allowed to be executed by using the keyword argument device
in the decorator when registering the function. The device argument is a list that can take 'cpu'
and 'gpu'
. The option indicates which implementation should be available and used. Hence, if there is no GPU on the server, using 'gpu'
would not work on the platform.
A function can also be made available on both the CPU and GPU by using device=['cpu', 'gpu']
.
For 'gpu'
, only NVIDIA GPUs that can handle CUDA instructions are currently supported.
Registering the Function
Once you define the functions—with appropriate signatures in the decorator—you have to register them to the HeavyDB. This is done automatically if the function is used in the same Python session. If multiple functions are defined in a file and need to be registered to be used by another process or user, then yo need to register them manually.
It is less efficient to call RemoteHeavyDB.register()
after every function declaration. Instead, use a single call after all functions are defined.
Similarly, you can clean the current session of all previously registered functions. The registration and unregistration of functions take into account only the functions defined in the current session associated with the object heavy
.
Using Registered Functions
To use the basic implementation of fahrenheit2celsius
:
To get the result of the function, you have to explicitly request execution on the server using the execute
method:
The execute
method is a convenience feature; it should not be used in production code. For production code, use heavyai or ibis via the ibis-heavyai backend to compose SQL queries using an ORM-like syntax.
Last updated