UDF Engines Configuration File (udf_engines.conf)
A UDF engine is a process that executes the code for UDFs. The engine runs on each node and can run as a stand-alone process or in a container.
The udf_engines.conf file defines the UDF engines that the X100 server should create and connect to on startup. If a defined engine cannot be connected to, the server startup is aborted.
The udf_engines.conf file is located in the II_SYSTEM/ingres/files directory on both Linux and Windows.
The format for the file is the same as vectorwise.conf except that each section name must be unique, and no section names are predefined. Each section defines one engine. Multiple sections with the same name are allowed if only one is enabled. The name of the default remote engine is [remote-process]. You can change this using the [system] udf_location_default parameter in the vectorwise.conf.
In the following Linux example, the X100 engine will launch a docker container.
[remote-container-linux]
enabled=1
name=remote
port=32225
host="127.0.0.1"
socket_retry=3
launch=1
processes=1
is_container=yes
pool_limit=16
command="/usr/bin/docker run -p $PORT:32225 --rm -m 512MB --mount type=bind,source=/opt/Actian/vectorwise-udf/log,target=/opt/Actian/vectorwise-udf/log,ro=0 --mount type=bind,source=/opt/Actian/vectorwise-udf/import,target=/opt/Actian/vectorwise-udf/import,ro=0 --name $INSTANCE_ID_udf_$SUB_ID --user $UID:$GID actian/vector7.0-udf-linux:1.0.x"
Last modified date: 12/19/2024