You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the feature and found no similar feature requirement.
Description
I have been in contact with StreamPark for a while now and have had a pretty good experience in terms of ease of use and stability. Currently, StreamPark itself supports UDF functions, but there doesn't seem to be a unified UDF management menu, so it is recommended to add a new UDF management menu for UDF management. The main purpose is to.
implement a unified management of new UDFs created by users (providing the main API for manipulating UDF objects).
Currently, SP uses UDF to upload UDF jar when creating jobs, but in the process of actual use, users may encounter some problems, such as: it is not clear what UDFs were created before, what the identififier is, etc. Therefore, the UDF management module can be used to solve these problems.
Usage Scenario
Note:
This feature is currently only implemented based on SQL jobs in Yarn Application mode;
The current plan is mainly based on the yarn application model, so the following is mainly idea of implement.
When creating a job, select the required UDF (e.g., a drop-down box showing the UDF available to the current user, associated with udfId);
When starting a job, it will query the paths of these udf stores according to the selected udfId (there can be more than one), and at the same time stitch these storage paths into strings, and finally pass them into yarn.provided.lib.dirs when submitting the job to achieve dynamic loading.
Actually, your plan is pretty much like zepplin's way of managing udf. I would like to contribute. Firstly, overall design for udf management.Secondly, stages to implement.
Search before asking
Description
I have been in contact with StreamPark for a while now and have had a pretty good experience in terms of ease of use and stability. Currently, StreamPark itself supports UDF functions, but there doesn't seem to be a unified UDF management menu, so it is recommended to add a new UDF management menu for UDF management. The main purpose is to.
implement a unified management of new UDFs created by users (providing the main API for manipulating UDF objects).
Currently, SP uses UDF to upload UDF jar when creating jobs, but in the process of actual use, users may encounter some problems, such as: it is not clear what UDFs were created before, what the identififier is, etc. Therefore, the UDF management module can be used to solve these problems.
Usage Scenario
Note:
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: