Open sfodor opened 9 months ago
Hello, thanks for bringing this to our attention.
This will be fixed in the next release. If you need to be unblocked sooner, you can use this patch:
diff --git a/sdk/search/search-documents/src/serviceUtils.ts b/sdk/search/search-documents/src/serviceUtils.ts
index bf2805cc49..c44644b728 100644
--- a/sdk/search/search-documents/src/serviceUtils.ts
+++ b/sdk/search/search-documents/src/serviceUtils.ts
@@ -653,14 +653,10 @@ export function publicSkillsetToGeneratedSkillset(
skillset: SearchIndexerSkillset,
): GeneratedSearchIndexerSkillset {
return {
- name: skillset.name,
- description: skillset.description,
- etag: skillset.etag,
- skills: skillset.skills,
+ ...skillset,
cognitiveServicesAccount: convertCognitiveServicesAccountToGenerated(
skillset.cognitiveServicesAccount,
),
- knowledgeStore: skillset.knowledgeStore,
encryptionKey: convertEncryptionKeyToGenerated(skillset.encryptionKey),
};
}
Describe the bug I've defined a SearchIndexerSkillset type skillset with two skills and with an indexProjections propetry. It seems when I call the indexerClient.createSkillset() with this definition, then all the configurations are applied to the new skillset except the indexProjections.
To Reproduce Steps to reproduce the behavior:
"indexProjections": { "selectors": [ { "targetIndexName": "vector-xxxxxxxxx", "parentKeyFieldName": "parent_id", "sourceContext": "/document/pages/*", "mappings": [ { "name": "chunk", "source": "/document/pages/*", "sourceContext": null, "inputs": [] }, { "name": "vector", "source": "/document/pages/*/vector", "sourceContext": null, "inputs": [] }, { "name": "title", "source": "/document/metadata_storage_name", "sourceContext": null, "inputs": [] } ] } ], "parameters": { "projectionMode": "skipIndexingParentDocuments" } },
Expected behavior The indexProjections is visible in the skillset config in the Azure portal.