-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Description
Support decoupling udf and be
Some of the UDFs used by users at their own business level are universal and can be used as third-party extension functions for other users with the same business scene.
But the current UDF is under the BE path. If there is a problem with the third-party UDF itself, it will also affect the compilation of the be.
For this reason I want to completely decouple the code and compilation process of UDF from BE.
The structure of the decoupled code is as follows:
be
custom_udf
CMakeFile.txt
src
udf_sample(source code)
Benefits after decoupling:
- UDF and BE compilation do not affect each other
- UDFs developed by users can also be fed back to the community. Other users with the same business scenario can also benefit.
Metadata
Metadata
Assignees
Labels
No labels