Project: ClickHouse (App Definition and Development / Database)
File: udf.md

slug: /en/sql-reference/functions/udf sidebar_position: 15 sidebar_label: UDF ClickHouse can call any external executable program or script to process data. The configuration of executable user defined functions can be located in one or more xml-files. The path to the configuration is specified in the parameter. A function configuration contains the following settings: `name` - a function name. `command` - script name to execute or command if `execute_direct` is false. `argument` - argument description with the `type`, and optional `name` of an argument. Each argument is described in a separate setting. Specifying name is necessary if argument names are part of serialization for user defined function format like or . Default argument name value is `c` + argument_number. `format` - a in which arguments are passed to the command. `return_type` - the type of a returned value. `return_name` - name of returned value. Specifying return name is necessary if return name is part of serialization for user defined function format like or . Optional. Default value is `result`. `type` - an executable type. If `type` is set to `executable` then single command is started. If it is set to `executable_pool` then a pool of commands is created. `maxcommandexecutiontime` - maximum execution time in seconds for processing block of data. This setting is valid for `executablepool` commands only. Optional. Default value is `10`. `commandterminationtimeout` - time in seconds during which a command should finish after its pipe is closed. After that time `SIGTERM` is sent to the process executing the command. Optional. Default value is `10`. `commandreadtimeout` - timeout for reading data from command stdout in milliseconds. Default value 10000. Optional parameter. `commandwritetimeout` - timeout for writing data to command stdin in milliseconds. Default value 10000. Optional parameter. `pool_size` - the size of a command pool. Optional. Default value is `16`. `sendchunkheader` - controls whether to send row count before sending a chunk of data to process. Optional. Default value is `false`. `executedirect` - If `executedirect` = `1`, then `command` will be searched inside userscripts folder specified by . Additional script arguments can be specified using whitespace separator. Example: `scriptname arg1 arg2`. If `execute_direct` = `0`, `command` is passed as argument for `bin/sh -c`. Default value is `1`. Optional parameter. `lifetime` - the reload interval of a function in seconds. If it is set to `0` then the function is not reloaded. Default value is `0`. Optional parameter. The command must read arguments from `STDIN` and must output the result to `STDOUT`. The command must process arguments iteratively. That is after processing a chunk of arguments it must wait for the next chunk. Example Creating `test_function` using XML configuration. File `testfunction.xml` (`/etc/clickhouse-server/testfunction.xml` with default path settings). ```xml <functions> <function> <type>executable</type> <name>testfunctionpython</name> <returntype>String</returntype> <argument> <type>UInt64</type> <name>value</name> </argument> <format>TabSeparated</format> <command>test_function.py</command> </function> </functions> ``` Script file inside `userscripts` folder `testfunction.py` (`/var/lib/clickhouse/userscripts/testfunction.py` with default path settings). ```python import sys if name == 'main': for line in sys.stdin: print("Value " + line, end='') sys.stdout.flush() ``` Query: ``` sql SELECT testfunctionpython(toUInt64(2)); ``` Result: ``` text testfunctionpython(2) Value 2 ``` Creating `testfunctionsum` manually specifying `execute_direct` to `0` using XML configuration. File `testfunction.xml` (`/etc/clickhouse-server/testfunction.xml` with default path

```xml <functions> <function> <type>executable</type> <name>testfunctionsum</name> <returntype>UInt64</returntype> <argument> <type>UInt64</type> <name>lhs</name> </argument> <argument> <type>UInt64</type> <name>rhs</name> </argument> <format>TabSeparated</format> <command>cd /; clickhouse-local --input-format TabSeparated --output-format TabSeparated --structure 'x UInt64, y UInt64' --query "SELECT x + y FROM table"</command> <executedirect>0</executedirect> </function> </functions> ``` Query: ``` sql SELECT testfunctionsum(2, 2); ``` Result: ``` text testfunctionsum(2, 2) 4 ``` Creating `testfunctionsum_json` with named arguments and format using XML configuration. File `testfunction.xml` (`/etc/clickhouse-server/testfunction.xml` with default path settings). ```xml <functions> <function> <type>executable</type> <name>testfunctionsum_json</name> <returntype>UInt64</returntype> <returnname>resultname</return_name> <argument> <type>UInt64</type> <name>argument_1</name> </argument> <argument> <type>UInt64</type> <name>argument_2</name> </argument> <format>JSONEachRow</format> <command>testfunctionsum_json.py</command> </function> </functions> ``` Script file inside `userscripts` folder `testfunctionsumjson.py` (`/var/lib/clickhouse/userscripts/testfunctionsumjson.py` with default path settings). ```python import sys import json if name == 'main': for line in sys.stdin: value = json.loads(line) firstarg = int(value['argument1']) secondarg = int(value['argument2']) result = {'resultname': firstarg + second_arg} print(json.dumps(result), end='\n') sys.stdout.flush() ``` Query: ``` sql SELECT testfunctionsum_json(2, 2); ``` Result: ``` text testfunctionsum_json(2, 2) 4 ``` Executable user defined functions can take constant parameters configured in `command` setting (works only for user defined functions with `executable` type). It also requires the `execute_direct` option (to ensure no shell argument expansion vulnerability). File `testfunctionparameterpython.xml` (`/etc/clickhouse-server/testfunctionparameterpython.xml` with default path settings). ```xml <functions> <function> <type>executable</type> <executedirect>true</executedirect> <name>testfunctionparameter_python</name> <returntype>String</returntype> <argument> <type>UInt64</type> </argument> <format>TabSeparated</format> <command>testfunctionparameterpython.py {testparameter:UInt64}</command> </function> </functions> ``` Script file inside `userscripts` folder `testfunctionparameterpython.py` (`/var/lib/clickhouse/userscripts/testfunctionparameterpython.py` with default path settings). ```python import sys if name == "main": for line in sys.stdin: print("Parameter " + str(sys.argv[1]) + " value " + str(line), end="") sys.stdout.flush() ``` Query: ``` sql SELECT testfunctionparameter_python(1)(2); ``` Result: ``` text testfunctionparameter_python(1)(2) Parameter 1 value 2 ``` Some functions might throw an exception if the data is invalid. In this case, the query is canceled and an error text is returned to the client. For distributed processing, when an exception occurs on one of the servers, the other servers also attempt to abort the query. In almost all programming languages, one of the arguments might not be evaluated for certain operators. This is usually the operators `&&`, `||`, and `?:`. But in ClickHouse, arguments of functions (operators) are always evaluated. This is because entire parts of columns are evaluated at once, instead of calculating each row separately. For distributed query processing, as many stages of query processing as possible are performed on remote servers, and the rest of the stages (merging intermediate results and everything after that) are performed on the requestor server. This means that functions can be performed on different servers. For example, in the query `SELECT f(sum(g(x))) FROM distributed_table GROUP BY h(y),` if a `distributed_table` has at least two shards, the functions g and h are performed on remote servers, and the function f is performed on the requestor server. if a `distributed_table` has only one shard, all the f, g, and h functions are performed on this shards server. The result of a function usually does not depend on which server it is performed on. However, sometimes this is important. For example, functions that work with dictionaries use the dictionary that exists on the server they are running on. Another example is the `hostName` function, which returns the name of the server it is running on in order to make `GROUP BY` by servers in a `SELECT` query. If a function in a query is performed on the requestor server, but you need to perform it on remote servers, you can wrap it in an any aggregate function or add it to a key in `GROUP BY`. Custom functions from lambda expressions can be created using the statement. To delete these functions use the statement.