Skip to content

Commit

Permalink
update changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
tsmith023 committed Aug 22, 2023
1 parent 2f00d71 commit 8a8172f
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions docs/changelog.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,22 +5,22 @@ Version 3.23.0
--------------
This minor version updates the client to work with Weaviate's 1.21 version and includes:

- Adds support for ``near<Media>`` filters when using the new ``multi2vec-bind`` module for neural searching on different media types.
- Adds support for ``near<Media>`` filters when using the new ``multi2vec-bind`` module for neural searching on different media types
- ``client.query.get().with_near_audio()``
- ``client.query.get().with_near_depth()``
- ``client.query.get().with_near_image()`` (unchanged from previous versions but usable by the module)
- ``client.query.get().with_near_imu()``
- ``client.query.get().with_near_thermal()``
- ``client.query.get().with_near_video()``
- Deprecates configuring ``client.batch`` using ``client.batch()`` in favour of using ``client.batch.configure()``.
- ``client.batch()`` will be removed in a future version.
- ``client.batch.configure()`` will return ``None`` in a future version.
- ``with client.batch as batch`` should be the standard way to initiate a batch.
- Adds support for new ``ContainsAny`` and ``ContainsAll`` filters when using ``.with_where``.
- Adds support for updating individual tenants within a multi-tenancy class configuration: ``client.schema.update_class_tenants``.
- Improves ``client.batch`` algorithm to choose batch size dynamically maximising throughput.
- Provides sensible defaults to ``client.batch`` that do not cause unexpected damaging consequences like infinite batch sizes.
- Fixes bugs when using ``.with_where`` with ``valueText``, ``valueString``, and ``valueGeoRange`` types.
- Deprecates configuring ``client.batch`` using ``client.batch()`` in favour of using ``client.batch.configure()``
- ``client.batch()`` will be removed in a future version
- ``client.batch.configure()`` will return ``None`` in a future version
- ``with client.batch as batch`` should be the standard way to initiate a batch
- Adds support for new ``ContainsAny`` and ``ContainsAll`` filters when using ``.with_where``
- Adds support for updating individual tenants within a multi-tenancy class configuration: ``client.schema.update_class_tenants``
- Improves ``client.batch`` algorithm to choose batch size dynamically maximising throughput
- Provides sensible defaults to ``client.batch`` that do not cause unexpected damaging consequences like infinite batch sizes
- Fixes bugs when using ``.with_where`` with ``valueText``, ``valueString``, and ``valueGeoRange`` types

Version 3.22.1
--------------
Expand Down

0 comments on commit 8a8172f

Please sign in to comment.