-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to weaviate-client to v4 #40194
Conversation
12f8cca
to
2b594c8
Compare
d83cb31
to
9b83e63
Compare
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! |
8dc6b31
to
de8b78c
Compare
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? |
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. |
de8b78c
to
8db59a4
Compare
d47fd91
to
54c1b7b
Compare
…n_configuration for consistency
176b60d
to
8f6f4ae
Compare
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.
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.
* 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
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.
Why
According to Weaviate Python client (v4) goes GA, the v3 client is now deprecated and we need to upgrade to v4
What
test_connections
create_class
tocreate_collection
get_schema
toget_collection_configuraiton
delete_classes
todelete_collections
query_with_vector
query_without_vector
toquery_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
validate_object
update_schema
create_schema
delete_all_schema
create_or_replace_classes
_compare_schema_subset
_convert_properties_to_dict
check_subset_of_schema
get_client
__init__
WeaviateDocumentIngestOperator
andWeaviateIngestOperator
to 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.rst
or{issue_number}.significant.rst
, in newsfragments.