completionConfig method not found

Google Cloud Build with AI Custom ML & MLOps
1

I’m trying to run Method: projects.locations.collections.dataStores.getCompletionConfig in Cloud Shell, and no matter the name specified, I keep getting an error.

  "error": {
    "code": 404,
    "message": "Method not found.",
    "status": "NOT_FOUND"
  }
}

Autocomplete does not work on my structured data store; requests return a 200 but an empty response.

I’m trying to debug, because it works on a different data store, and this call seems appropriate for understanding the issue.

Is the method available? What are the possible causes for autocomplete being disabled on a data store? The issue has persisted for months, so it doesn’t seem like a question of time.

2

Hey,

Hope you’re keeping well.

The projects.locations.collections.dataStores.getCompletionConfig method isn’t part of the public Discovery Engine API, which is why you’re getting a 404 Method not found error. Autocomplete in Vertex AI Search/Discovery Engine is enabled or disabled per data store via its completionConfig settings when the data store is created or updated.

If autocomplete works on one data store but returns empty results on another, check in the Console under Discovery Engine → your data store → Autocomplete to confirm it’s enabled and that there’s ingested data supporting suggestions. Also verify the serving config you’re calling in your autocomplete request is linked to the correct data store, since autocomplete responses depend on that association. If you need to change the configuration, use the projects.locations.collections.dataStores.update endpoint with the proper completionConfig payload rather than trying to query it directly.

Thanks and regards,
Taz

3

Hi @iTazB

Thank you, I really appreciate the reply.

I had double checked in the console as suggested but was hitting a dead end. Everything looked right. I submitted feedback using the thumbs.

As of today, with no action taken on my part, and using the same serving config as always, autocomplete is no longer returning empty responses and is working (in preview and via the API) on both datastores for which it was not, so that is good news for me.

I am a tad confused by your response, because I can’t find the update endpoint in the public docs for the REST api nor do I see a reference to the completionConfig in the patch method.

Anyways, all’s well that ends well, so thanks again for the pointers.

Regards,

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.