Upgrade to weaviate-client to v4 #40194
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lee-W
force-pushed
the
upgrade-to-weaviate-v4
branch
10 times, most recently
from
12f8cca to
2b594c8
Compare
Lee-W
force-pushed
the
upgrade-to-weaviate-v4
branch
from
d83cb31 to
9b83e63
Compare
Member
Author
|
Hi @eladkal , if my memory serves me right, when we make a PR with breaking changes to a provider, we need to mark it somewhere. Could you please point out where I should mark it? Thanks! |
Lee-W
force-pushed
the
upgrade-to-weaviate-v4
branch
from
8dc6b31 to
de8b78c
Compare
Member
In provider's CHANGELOG.rst (see comment at the top of it). But is it really a breaking change for the users of the Hook/Operator? |
Member
|
Looked at it - there are many changes and it does look like breaking looking at the few of those. In CHANGELOG you should describe what the users of previous version should do to migrate to this one. |
Lee-W
force-pushed
the
upgrade-to-weaviate-v4
branch
from
de8b78c to
8db59a4
Compare
phanikumv
requested review from
Taragolis,
pankajastro,
pankajkoti,
sunank200,
utkarsharma2 and
vatsrahul1001
Lee-W
force-pushed
the
upgrade-to-weaviate-v4
branch
4 times, most recently
from
d47fd91 to
54c1b7b
Compare
…n_configuration for consistency
Lee-W
force-pushed
the
upgrade-to-weaviate-v4
branch
from
176b60d to
8f6f4ae
Compare
52 tasks
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Jul 9, 2024
The apache#40194 by mistake replaced 1.4.2 version with 2.0.0 rather than adding it - this caused that 1.4.2 changes have been incorporated into 2.0.0 and 1.4.2 is missing from the changelog. This PR brings 1.4.2 back.
potiuk
added a commit
that referenced
this pull request
Jul 9, 2024
The #40194 by mistake replaced 1.4.2 version with 2.0.0 rather than adding it - this caused that 1.4.2 changes have been incorporated into 2.0.0 and 1.4.2 is missing from the changelog. This PR brings 1.4.2 back.
27 tasks
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Jul 26, 2024
* update min weaviate-client version to 4.4.0
* weaviate hook
* update airflow connection to v4 style
* migrate the following methods to v4 API
* `test_connections`
* `create_class` to `create_collection`
* `get_schema` to `get_collection_configuraiton`
* `delete_classes` to `delete_collections`
* `query_with_vector`
* `query_without_vector` to `query_with_text`
* `create_object`
* `get_object`
* `delete_object`
* `update_object`
* `replace_object`
* `object_exists`
* `batch_data`
* `get_or_create_object`
* `update_collection_configuration`
* `_generate_uuids`
* `create_or_replace_document_objects`
* `_delete_objects`
* `_delete_all_documents_objects`
* `_get_documents_to_uuid_map`
* `_get_segregated_documents`
* remove the following methods which are no longer supported in v4 API
* `validate_object`
* `update_schema`
* `create_schema`
* `delete_all_schema`
* `create_or_replace_classes`
* `_compare_schema_subset`
* `_convert_properties_to_dict`
* `check_subset_of_schema`
* remove deprecated method `get_client`
* remove unused argument retry_status_codes in `__init__`
* weaviate operators
* migrate `WeaviateDocumentIngestOperator` and `WeaviateIngestOperator` to use hook with v4 API
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Jul 26, 2024
The apache#40194 by mistake replaced 1.4.2 version with 2.0.0 rather than adding it - this caused that 1.4.2 changes have been incorporated into 2.0.0 and 1.4.2 is missing from the changelog. This PR brings 1.4.2 back.
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
According to Weaviate Python client (v4) goes GA, the v3 client is now deprecated and we need to upgrade to v4
What
test_connectionscreate_classtocreate_collectionget_schematoget_collection_configuraitondelete_classestodelete_collectionsquery_with_vectorquery_without_vectortoquery_with_textcreate_objectget_objectdelete_objectupdate_objectreplace_objectobject_existsbatch_dataget_or_create_objectupdate_collection_configuration_generate_uuidscreate_or_replace_document_objects_delete_objects_delete_all_documents_objects_get_documents_to_uuid_map_get_segregated_documentsvalidate_objectupdate_schemacreate_schemadelete_all_schemacreate_or_replace_classes_compare_schema_subset_convert_properties_to_dictcheck_subset_of_schemaget_client__init__WeaviateDocumentIngestOperatorandWeaviateIngestOperatorto use hook with v4 API^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.