Migrating to Pinecone Client v9.0.1
Version v9.0.1 introduces 2 breaking changes. This guide details how to update your code.
Released: 5/19/2026
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
grpc_index.create_namespacegrpc_index.describe_namespacegrpc_index.delete_namespacegrpc_index.list_namespacesgrpc_index.list_namespaces_paginatedIndex.searchAsyncIndex.searchpc.preview.indexes.describe_backuppc.indexes.configurepc.assistants.createIndexModel.private_hostByocSpecInfo.schemaPreviewIndexes.createPreviewIndexes.configurePreviewIndexModelpc.assistants.chatpinecone.__init__.pyiPreviewTextQuery.fieldPreviewTextQuery.fieldsGrpcIndex.querypc.inference.rerankIndex.fetch_by_metadataupsert_recordspc.collections.createProjects.createProjects.updateApiKeys.createPreviewDocuments.fetchPreviewDocuments.deleteBreaking Changes
●Issue #1
The parameters `filter` on `PreviewDocuments.fetch` and `PreviewDocuments.delete` have been removed. If you were passing `filter=` to these methods in v9.0.0, the call will now raise a `TypeError` as the argument was ignored by the backend.
●Issue #2
Code that explicitly caught `grpc.RpcError` to handle gRPC timeouts will no longer catch `Cancelled` + `"Timeout expired"` errors from the gRPC backend, as these are now raised as the higher-level `PineconeTimeoutError`.
Migration Steps
- 1If you relied on passing `filter=` to `PreviewDocuments.fetch` or `PreviewDocuments.delete`, remove that argument from your calls.
- 2If you had custom error handling that specifically caught `grpc.RpcError` to handle timeouts, ensure you also catch `PineconeTimeoutError` if you need to handle gRPC timeouts specifically.
Release Summary
Version 9.0.1 is a polish release restoring several missing gRPC namespace APIs and search query features from v9.0.0, widening public input types for better ergonomics, and adding client-side validation checks.
Need More Details?
View the full release notes and all changes for Pinecone Client v9.0.1.
View Full Changelog