Release Note (3.27.2)

Release time: 2024-07-23 14:50:49

🙇 We'd like to thank all contributors for this new release! In particular,
Joan Fontanals, Jina Dev Bot, 🙇

🐞 Bug fixes

• [6e29377a] - fix optim issue with optimization (#6184) (Joan Fontanals)

🍹 Other Improvements

• [268ceb76] - version: the next version will be 3.27.2 (Jina Dev Bot)

Release Note (3.27.1)

Release time: 2024-07-23 11:45:04

🙇 We'd like to thank all contributors for this new release! In particular,
Joan Fontanals, Jina Dev Bot, 🙇

🐞 Bug fixes

• [4eaeb2da] - set direct docs (#6183) (Joan Fontanals)

🍹 Other Improvements

• [b28c633a] - docs: update TOC (Jina Dev Bot)
• [b0fe4102] - version: the next version will be 3.27.1 (Jina Dev Bot)

Release Note (3.27.0)

Release time: 2024-07-18 17:00:58

This release contains 1 new feature.

🆕 Features

Add flush-all parameter to dynamic batching configuration (#6179)

You can pass flush_all=True``to the dynamic_batchingconfiguration which will allow to pass all the dynamically batched documents at once to the Executor. This makespreferred_batch_size` parameter a parameter that triggers the flushing but that can be bypassed.

🤟 Contributors

We would like to thank all contributors to this release:

• Joan Fontanals (@JoanFM )

Release Note (3.26.0)

Release time: 2024-07-10 17:04:59

This release contains 1 new feature and 2 fixes.

🆕 Features

Enable use of Python rotating logging handlers (#6167)

You can now use rotating logging handlers:

handlers:
  - RotatingFileHandler
level: INFO
configs:
  RotatingFileHandler:
    filename: './logs/myapp_rotating.log'
    maxBytes: 20000000  # 20MB
    backupCount: 10
    encoding: utf-8
    formatter: JsonFormatter

🐞 Bug Fixes

Raise Exception if dynamic batching is activated with parameters annotation (#6176)

If an Executor in an endpoint requires parameters, this is incompatible with the use of dynamic_batching for that specific endpoint. This setting will fail.

Allow passing headers to client when using http (#6177)

🤟 Contributors

We would like to thank all contributors to this release:

• Janus Xu (@Janus-Xu)
• Joan Fontanals (@JoanFM )

Release Note (3.25.2)

Release time: 2024-06-13 16:32:38

🙇 We'd like to thank all contributors for this new release! In particular,
Joan Fontanals, Zac Li, Jina Dev Bot, 🙇

🐞 Bug fixes

• [ae142c00] - update force-release.yml (#6172) (Joan Fontanals)
• [98429b05] - support sagemaker batch transform for clip (#6171) (Zac Li)

🏁 Unit Test and CICD

• [7e2247d2] - update force-release.yml (#6173) (Joan Fontanals)
• [12e2a945] - test ci (#6169) (Joan Fontanals)

🍹 Other Improvements

• [9dcd0c18] - docs: update TOC (Jina Dev Bot)
• [287fa618] - version: the next version will be 3.25.2 (Jina Dev Bot)

Release Note (3.25.1)

Release time: 2024-04-10 14:39:02

This release contains 1 bug fix.

🐞 Bug Fixes

Fix input schema with --provider Azure (#6163)

When using --provider Azure, there was an error when using the input schema of an incorrect endpoint.

We would like to thank all contributors to this release:

• Joan Fontanals (@JoanFM)

Release Note (3.25.0)

Release time: 2024-04-02 13:02:31

This release contains 1 new feature.

🆕 Features

Executor to run in a Microsoft Azure custom container (#6159)

Executors can now run as a FastAPI app in a Microsoft Azure container when being served with AZURE as the provider argument.

🤟 Contributors

We would like to thank all contributors to this release:

• Zac Li (@zac-li )

Release Note (3.24.1)

Release time: 2024-03-20 09:35:52

This release contains 3 bug fixes.

🐞 Bug Fixes

Fix Flow deployment of Model with float field (#6155)

When serving a Flow with HTTP, serving failed because the model reconstructed in the Gateway interpreted the float field as an array. Now the model served in the Gateway uses the correct schema.

Expose only /invocations endpoint when serving with --provider SAGEMAKER (#6152)

When exposing an Executor with SAGEMAKER as the provider argument, only the /invocations endpoint should be used. However, previously all other endpoints were also exposed. This is now fixed.

Optional parameters when typed parameter has all default fields (#6152)

When using a strongly typed parameters argument with the Executor endpoint, even if the parameters model type had all fields with default values and not required, you still needed to pass an empty parameters={} field to the call when serving via HTTP. With this change, you no longer need to pass this empty dictionary.

🤟 Contributors

We would like to thank all contributors to this release:

• Joan Fontanals (@JoanFM)

Release Note (3.24.0)

Release time: 2024-03-11 09:48:35

This release contains 1 new feature.

🆕 Features

Support provider endpoint in Jina Executor (#6149)

This release adds the --provider-endpoint flag, which can only be used in conjunction with the --provider flag. The --provider-endpoint flag takes as a parameter a named endpoint supported in the Executor and sets the endpoint of the provider to map to that Executor endpoint.

At present, SageMaker is the only available provider option, so using the parameters --provider SAGEMAKER --provider-endpoint <named endpoint> will make the SageMaker invocations endpoint map to the named endpoint of the Executor.

🤟 Contributors

We would like to thank all contributors to this release:

• Zac Li (@zac-li )

Release Note (3.23.5)

Release time: 2024-02-29 14:36:02

This release contains 1 bug fix.

🐞 Bug Fixes

Fix batch transform endpoint for SageMaker with nested schemas (#6145)

This release improves the SageMaker Batch Transform input data parsing logic so that data with more complex schema can be interpreted as expected.

🤟 Contributors

We would like to thank all contributors to this release:

• Zac Li (@zac-li )