Remote User Defined Function Service

User Defined Function Rpc

Remote UDF Service The Remote UDF Service can be accessed through RPC to implement the execution of user-defined functions. Compared with Native UDF implementations, Remote UDF Service has the following advantages and limitations:

1. The advantage

   • Cross-language: UDF services can be written in all languages supported by Protobuf.
   • Security: UDF execution failure or crash only affects the UDF Service and does not cause the Doris process to crash.
   • Flexibility: Any other Service or library class can be invoked within a UDF Service to meet a wider variety of business requirements.

2. Restrictions on use

   • Performance: Compared to Native UDFs, UDF services incur extra network overhead and thus have much lower performance than Native UDFs. At the same time, the implementation of the UDF Service also affects the execution efficiency of the function. Users need to deal with problems such as high concurrency and thread safety by themselves.
   • Single line mode and batch mode: Doris's original query execution framework based on row memory would execute one UDF RPC call for each row of data, so the execution efficiency was very poor. However, under the new vectorization execution framework, one UDF RPC call would be executed for each batch of data (2048 rows by default), so the performance was significantly improved. In actual tests, the performance of Remote UDF based on vectorization and batch processing is similar to that of Native UDF based on rowmemory, which can be used for reference.

Write UDF functions

This section describes how to develop a Remote RPC Service. Samples for the Java version are provided under samples/doris-demo/udf-demo/ for your reference.

Copy the proto file

Copy gensrc/proto/function_service.proto and gensrc/proto/types.proto to Rpc service

• function_service.proto
  • PFunctionCallRequest
    • function_name：The function name, corresponding to the symbol specified when the function was created
    • args：The parameters passed by the method
    • context：Querying context Information
  • PFunctionCallResponse
    • result：Return result
    • status：Return Status, 0 indicates normal
  • PCheckFunctionRequest
    • function：Function related information
    • match_type：Matching type
  • PCheckFunctionResponse
    • status：Return status, 0 indicates normal

Generated interface

Use protoc generate code, and specific parameters are viewed using protoc -h

Implementing an interface

The following three methods need to be implemented

• fnCall：Used to write computational logic
• checkFn：Used to verify function names, parameters, and return values when creating UDFs
• handShake：Used for interface probe

Create UDF

Currently UDTF are not supported

CREATE FUNCTION 
name ([,...])
[RETURNS] rettype
PROPERTIES (["key"="value"][,...])  

Instructions:

1. PROPERTIES中symbolRepresents the name of the method passed by the RPC call, which must be set.
2. PROPERTIES中object_fileRepresents the RPC service address. Currently, a single address and a cluster address in BRPC-compatible format are supported. Refer to the cluster connection modeFormat specification.
3. PROPERTIES中typeIndicates the UDF call type, which is Native by default. Rpc is transmitted when Rpc UDF is used.
4. name: A function belongs to a DB and name is of the formdbName.funcName. When dbName is not explicitly specified, the db of the current session is useddbName.

Sample:

CREATE FUNCTION rpc_add_two(INT,INT) RETURNS INT PROPERTIES (
  "SYMBOL"="add_int_two",
  "OBJECT_FILE"="127.0.0.1:9114",
  "TYPE"="RPC"
);
CREATE FUNCTION rpc_add_one(INT) RETURNS INT PROPERTIES (
  "SYMBOL"="add_int_one",
  "OBJECT_FILE"="127.0.0.1:9114",
  "TYPE"="RPC"
);
CREATE FUNCTION rpc_add_string(varchar(30)) RETURNS varchar(30) PROPERTIES (
  "SYMBOL"="add_string",
  "OBJECT_FILE"="127.0.0.1:9114",
  "TYPE"="RPC"
);

Use UDF

Users must have the SELECT permission of the corresponding database to use UDF/UDAF.

The use of UDF is consistent with ordinary function methods. The only difference is that the scope of built-in functions is global, and the scope of UDF is internal to DB. When the link session is inside the data, directly using the UDF name will find the corresponding UDF inside the current DB. Otherwise, the user needs to display the specified UDF database name, such as dbName.funcName.

Delete UDF

When you no longer need UDF functions, you can delete a UDF function by the following command, you can refer to DROP FUNCTION.

Example

Examples of rpc server implementations and cpp/java/python languages are provided in the samples/doris-demo/ directory. See the README.md in each directory for details on how to use it. For example, rpc_add_string

mysql >select rpc_add_string('doris');
+-------------------------+
| rpc_add_string('doris') |
+-------------------------+
| doris_rpc_test          |
+-------------------------+

The logs will be displayed.

INFO: fnCall request=function_name: "add_string"
args {
  type {
    id: STRING
  }
  has_null: false
  string_value: "doris"
}
INFO: fnCall res=result {
  type {
    id: STRING
  }
  has_null: false
  string_value: "doris_rpc_test"
}
status {
  status_code: 0
}