Should Java worker load cx code at worker start up?
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
Dotnet worker, python worker both have reference to cx code at worker start up, this brings a lot of flexibility into worker implementation and when adding new features to worker and also improve java worker performance (as load cx logics will only be executed once. Right now, this logics is executed for each function load request). Java worker should some how consider the same way.
Python worker has an app setting (env var) point to cx script once app is deployed. We may consider the same pattern here.
Node worker is rely on function_app_directory which is already available WorkerInitRequest. This should be a better approach.
Updates: we can use worker index feature provided by host.
- Dominant language
- Java
- Stars
- 103
- Forks
- 74
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/azure-functions-java-worker
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
mcp-extension
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
mcp-extension
Azure/azure-functions-java-worker#863 · 1 assignee ·
All issues in Azure/azure-functions-java-worker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100