The information below includes all information one needs to know to begin running Java UDFs. For more information on writing Java UDFs, see Java UDF API; for more information on simulating running UDFs, see UDF Simulator. Example Java UDFs can be found here.
Though any of the native APIs can be used for running UDFs written in any UDF API language, all the examples below are written using the native Java API.
Calling the createProc() method will deploy the specified UDF to the Kinetica execution environment, to every server in the cluster. The method takes the following parameters:
|procName||A system-wide unique name for the UDF|
|executionMode||An execution mode; either distributed or nondistributed|
A set of files composing the UDF package, including the names of the files and the binary data for those files. The files specified will be created on the target Kinetica servers in the UDF directory (default is the /opt/gpudb/procs/ directory, governed by the proc_directory configuration parameter), with the given data and filenames; if the filenames contain subdirectories, that structure will be copied to the target servers
Files in Kinetica File System (KiFS) can also be used here. To use a KiFS file, pass the KiFS URI as the name of the file and leave the binary data portion empty. In this case, the KiFS files will be copied into the UDF directory for use when executeProc() is called.
Uploading files using the files parameter should be reserved for smaller files; larger files should be uploaded to KiFS and referenced there instead.
|command||The name of the command to run, which can be a file within the deployed UDF fileset, or any command able to be executed within the host environment, e.g., java. If a host environment command is specified, the host environment must be properly configured to support that command's execution.|
|args||A list of command-line arguments to pass to the specified command; e.g., -cp <class path> <class name> or -jar <file name.jar>|
|options||Optional parameters for UDF creation; see createProc() for details|
For example, to deploy a Java UDF using the native Java API, a local, compiled proc jar (output/kinetica-udf-table-copy-proc-jar-with-dependencies.jar) will need to be read in as bytes and then passed into the createProc() call as a value paired with the file name as its key inside map files. A Java class path argument (-jar output/kinetica-udf-table-copy-proc-jar-with-dependencies.jar) is also provided.
To use the same files, located in a KiFS directory named udf instead, initialize files as follows:
The max_concurrency_per_node setting is available in the options map of the /create/proc. This option allows you to define a per-Kinetica- host concurrency limit for a UDF, i.e. no more than n OS processes (UDF instances) in charge of evaluating the UDF will be permitted to execute concurrently on a single Kinetica host. You may want to set a concurrency limit if you have limited resources (like GPUs) and want to avoid the risks of continually exhausting your resources. This setting is particularly useful for distributed UDFs, but it will also work for non-distributed UDFs.
You can also set concurrency limits on the Edit Proc screen in the UDF section of GAdmin
The default value for the setting is 0, which results in no limits. If you set the value to 4, only 4 instances of the UDF will be queued to execute the UDF. This holds true across all invocations of the proc; this means that even if /execute/proc is called eight times, only 4 processes will be running. Another instance will be queued as soon as one instance finishes processing. This process will repeat, only allowing 4 instances of the UDF to run at a time, until all instances have completed or the UDF is killed.
Calling the executeProc() method will execute the specified UDF within the targeted Kinetica execution environment. The method takes the following parameters:
|procName||The system-wide unique name for the UDF|
|params||Set of string-to-string key/value paired parameters to pass to the UDF|
|binParams||Set of string-to-binary key/value paired parameters to pass to the UDF|
|inputTableNames||Input data table names, to be processed by the UDF|
|inputColumnNames||Mapping of input data table names to their respective column names, to be processed as input data by the UDF|
|outputTableNames||Output data table names, where processed data is to be appended|
|options||Optional parameters for UDF execution; see executeProc() for details|
The call is asynchronous and will return immediately with a run_id, which is a string that can be used in subsequent checks of the execution status.
For example, to execute a proc that's already been created (UdfTcJavaProc) using existing input (udf_tc_java_in_table) and output (udf_tc_java_out_table) tables:
UDFs can be managed using either GAdmin or one of the methods below:
- deleteProc() -- removes the given UDF definition from the system; needs to be called before createProc() when recreating a UDF
- hasProc() -- returns whether the given UDF exists
- killProc() -- terminates a running UDF (or UDFs)
- showProc() -- returns the parameter values used in creating the UDF
- showProcStatus() -- Returns whether the UDF (or UDFs) is still running, has completed, or has exited with an error, along with any processed results