Immutable solution version
Vertex AI Vector Search: index_id is only valid for api_version='v1', v2 uses collections (llamaindex_v2_migration)
Complete solution
dont mix v1 and v2 params.
Vertex AI Vector Search: indexid is only valid for apiversion='v1', v2 uses collections (llamaindexv2migration)
TL;DR
[LlamaIndex Vector Search v2 migration guide]: dont mix v1 and v2 params. indexid with apiversion='v2' fails with 'indexid is only valid for apiversion='v1''. v2 uses collections instead of index plus endpoint, and v2 ops need the google-cloud-vectorsearch package (pip install the [v2] extra).
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
If you want old behavior back, set VERTEXAIENABLE_V2 to false.
Context: LlamaIndex Vector Search v2 migration guide: v1 and v2 parameters cannot be mixed. Passing indexid with apiversion='v2' fails with indexid is only valid for apiversion='v1'. v2 uses collections, not index plus endpoint, and v2 operations need the google-cloud-vectorsearch package installed. To force the old behavior, set the VERTEXAIENABLE_V2 environment variable to false. v1 clear() is not supported; v2 supports it.
Evidence
Source: LlamaIndex Vector Search v2 migration guide: v1 and v2 parameters cannot be mixed. Passing indexid with apiversion='v2' fails with indexid is only valid for apiversion='v1'. v2 uses collections, not index plus endpoint, and v2 operations need the google-cloud-vectorsearch package installed. To force the old behavior, set the VERTEXAIENABLE_V2 environment variable to false. v1 clear() is not supported; v2 supports it.
Verified resolution: [LlamaIndex Vector Search v2 migration guide]: dont mix v1 and v2 params. indexid with apiversion='v2' fails with 'indexid is only valid for apiversion='v1''. v2 uses collections instead of index plus endpoint, and v2 ops need the google-cloud-vectorsearch package (pip install the [v2] extra). If you want old behavior back, set VERTEXAIENABLE_V2 to false.
Source URL: https://github.com/run-llama/llamaindex/blob/HEAD/llama-index-vector-stores-vertexaivectorsearch/V2MIGRATION.md
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_2Jr-p1oGDU48kT03YyIUmA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Vertex AI Vector Search: index_id is only valid for api_version='v1', v2 uses collections (llamaindex_v2_migration) <span>— Vectle</span></a>