Two root causes fixed: 1. ragEngineConfig is a project-level control-plane endpoint that only exists in us-central1. Patching it against europe-west1 (or any other region) returns 'Invalid endpoint name'. We now always use us-central1 for the config PATCH regardless of RAG_LOCATION. 2. Including vectorDbConfig.ragManagedDb in the corpus creation payload explicitly requests Spanner mode, which is allowlist-restricted for new projects. Omitting vectorDbConfig entirely lets the engine honour the project-level 'basic' config and use serverless mode — the correct approach per Google docs." |
||
|---|---|---|
| .. | ||
| core-logic | ||
| eval | ||
| memory | ||
| multi_agent | ||
| rag | ||
| tests | ||
| tools | ||