Vertex AI Matching Engine proto conflicts with google.cloud.aiplatform
See original GitHub issueHello Google Team,
I have a Cloud Run service that’s calling Vertex AI Matching Engine grpc endpoint. As soon as install pip install google-cloud-aiplatform
and import aiplatform from google.cloud import aiplatform
it fails with the following error message.
"match_service.proto": google.cloud.aiplatform.container.v1beta1.MatchRequest
is already defined in file "google/cloud/aiplatform/matching_engine/_protos/match_service.proto".
Which makes sense because the proto files also contain the package
package google.cloud.aiplatform.container.v1beta1;
package version: google-cloud-aiplatform 1.14.0
Any suggestions?
Issue Analytics
- State:
- Created a year ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Package google.cloud.aiplatform.v1 | Vertex AI
Vertex AI Vizier is a service to solve blackbox optimization problems, ... The operation metadata with regard to Matching Engine Index operation.
Read more >google-cloud-aiplatform - PyPI
Vertex AI : Google Vertex AI is an integrated suite of machine learning tools and services for building and using ML models with...
Read more >aiplatform - Go Packages
Package aiplatform aliases all exported identifiers in package "cloud.google.com/go/aiplatform/apiv1beta1/aiplatformpb".
Read more >apache-airflow-providers-google Documentation
google -cloud-aiplatform. >=1.7.1,<2.0.0 ... Add system tests for Vertex AI operators in new approach (#27053) ... Cloud ML Engine operators assets (#26836) ...
Read more >All you need to know about Google Vertex AI Matching Engine
This JSON file contains now the vector representation of our sentences. As the next step, we store it in Google Cloud Storage. That's...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi, are you importing match_service_pb2 generated by yourself as instructed in this notebook?
Can you try importing the match_service_pb2 in the SDK:
That notebook is not using this SDK and does not have the conflict problem. It only happens when you use SDK together with the manually generated grpc client library.
Another method you can do is to use the match method provided by the SDK: https://github.com/googleapis/python-aiplatform/blob/main/google/cloud/aiplatform/matching_engine/matching_engine_index_endpoint.py#L902
Example can be found in this notebook: https://github.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/official/matching_engine/sdk_matching_engine_for_indexing.ipynb
However, it doesn’t support filtering and crowding right now.