Skip to content

Releases: Azure/azure-functions-java-worker

Azure Functions Java Worker 1.8.1

10 Dec 04:37
5ad272c
Compare
Choose a tag to compare

This Release includes:

  • CI Improvement #402
  • Update for Distributed Tracing #411

This release is for internal improvement. No new feature for users.
We update CI pipeline, End-To-End testing. With introducing the %AZURE_FUNCTIONS_MESH_JAVA_OPTS% in the worker.config.json . This argument is not allowed to modify by users. Internal use only.

Azure Functions Java Worker 1.8.0

15 Sep 21:47
e1c2809
Compare
Choose a tag to compare

This release includes:

  • Unshard Gson #399
  • Upgrade Java Functions Library to 1.4.0 #401

We have some issues related shading. We fully shaded however, Gson could be an issue since it is exposed indirectly and `HttpResponseMessage.Builder' 'body' method using Gson internally with shaded version. If you use Gson annotation, the last version will ignore the annotation. So we decided shaded bach the Gson.

This will fix following issues:

  • Java Function Host failing with Class Cast Exception #396
  • Gson annotation is ignored #400

Azure Functions Java Worker 1.7.3-SNAPSHOT

31 Jul 02:48
Compare
Choose a tag to compare

Bug fixes #393

This release includes:

1.7.2 Release

  • Update Azure Functions Java Library for Kafka and EventGrid (Azure Functions Java Library 1.4.0-SNAPSHOT)
  • Adding E2E testing for Kafka and EventGrid

1.7.1 Features that includes sharding all worker jars.

Azure Functions Java Worker 1.7.2-SNAPSHOT

24 Jul 00:23
Compare
Choose a tag to compare

This release includes 1.7.1 features that includes sharding all worker jars.

Azure Functions Java Worker 1.7.1

25 Jun 20:33
Compare
Choose a tag to compare

This release is for shading all worker jars. This will give the option to clients to override the current behavior for java worker for how the jars are load it.

Only for JAVA 8
To be a backward compatible We freeze all the jars we currently have added to lib_worker_1.6.2.
We still load the worker jars first then the client jars.

If the client like to reverse this order and their jars takes presence first, they will need to add FUNCTIONS_WORKER_JAVA_LOAD_APP_LIBS True or 1. By this way it will be opt-in and load their jars first then worker jars.

JAVA 11 will use only the customer jars.

Azure Functions Java Worker 1.6.2

17 Jun 22:55
Compare
Choose a tag to compare

Allows using environment variables in worker.config.json.

Azure Functions Java Worker 1.6.1

22 May 17:45
Compare
Choose a tag to compare

Throughput improvements by Supporting RpcHttpBodyOnly and RpcHttpTriggerMetadataRemoved

Azure Functions Java Worker 1.6.0

29 Apr 19:10
Compare
Choose a tag to compare
  • Increase gRpc channel message size to Integer.MaxValue
  • Add the support for WorkerStatus.
  • Add initial support for java 11 runtime.

Azure Functions Java Worker 1.5.2-SNAPSHOT

21 Sep 02:00
Compare
Choose a tag to compare

Release Notes

  • Added support for TraceContext on ExecutionContext.
  • Added Azure Pipelines for Nightly builds.

Azure Functions Java Worker 1.5.10246

26 Jul 01:28
Compare
Choose a tag to compare

Release Notes

  • Added support of Typed Data collections
  • Added Azure Pipelines for Nightly builds