Skip to content

@azure/search-documents createSkillset(): the indexProjections part of the skillset config is not applied #28478

Open

Description

  • Package Name: @azure/search-documents
  • Package Version: "12.0.0-alpha.20240126.1"
  • Operating system: Windows 11
  • nodejs
    • version: v18.16.0 / v18.19.0
  • browser
    • name/version:
  • typescript
    • version: 4.9.4
  • Is the bug related to documentation in

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:

  1. Create a SearchIndexerSkillset type skillset with indexProjections like
    "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" } },
  2. Call createSkillset() with this configuration.
  3. The call is executed without any error or warning.
  4. The indexProjections is missing from the skillset config in the Azure portal.

Expected behavior
The indexProjections is visible in the skillset config in the Azure portal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Searchcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

  • Status

    Untriaged

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions