Weaviate: Weaviate Python Client: v3 API deprecation - migrate to v4 | SignalBreak

Weaviate: Weaviate Python Client: v3 API deprecation - migrate to v4 | SignalBreak | SignalBreak

Source text

Introduction All good things have to come to an end. In this case, it's time for us to start saying goodbye to the v3 API in our Weaviate Python client . You probably know that the Weaviate Python client got a glow-up to an extensively re-written (and improved) v4 API around six months ago . This brought more speed through gRPC and improved usability through expanded IDE support and additional type-safety. Here's an illustrative example of the difference between the two versions. Note how little of the v4 API is based on raw strings, and how much more is based on type-safe objects: Python Client v4 Python Client v3 from weaviate . classes . config import Configure , Property , DataType , VectorDistances , VectorFilterStrategy client . collections . create ( "Article" , # Additional configuration not shown vector_index_config = Configure . VectorIndex . hnsw ( quantizer = Configure . VectorIndex . Quantizer . bq ( ) , ef_construction = 300 , distance_metric = VectorDistances . COSINE , filter_strategy = VectorFilterStrategy . SWEEPING # or ACORN (Available from Weaviate v1.27.0) ) , ) API docs class_obj = { 'class' : 'Article' , # Additional configuration not shown "vectorIndexType" : "flat" , "vectorIndexConfig" : { "bq" : { "enabled" : True , # Enable BQ compression. Default: False "rescoreLimit" : 200 , # The minimum number of candidates to fetch before rescoring. Default: -1 (No limit) "cache" : True , # Enable use of vector cache. Default: False } , "vectorCacheMaxObjects" : 100000 , # Cache size if `cache` enabled. Default: 1000000000000 "filterStrategy" : "sweeping" # or "acorn" (Available from Weaviate v1.27.0) } } client . schema . create_class ( class_obj ) API docs Deprecated (v3) The v4 API is a significant improvement over the v3 API, and we want to encourage all of our users to migrate to the new version. Having said that, we appreciate that code migration isn't an overnight task. So the v4 client versions had included the older v3 API in order to eas

View original source

Weaviate Python Client: v3 API deprecation - migrate to v4

More from Weaviate

Get alerts for Weaviate