"Invalid index schema" error in Azure portal

[tjcrowder]

Thank you for this comprehensive sample.

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Deploy the sample application
2. Navigate to the blade for gptkbindex in Azure

When I do that, I see a warning and an error:

The warning is:

This index has vector fields created using the 2023-07-01-preview definition. It can't be edited using new API versions. We recommend that you migrate it to use vector profiles to restore full portal functionality.

It has a "Migrate" button next to it.

The error is:

Invalid index schema: fields[2].vectorSearchProfile - The value must not be empty.

Using the "Migrate" button in the UI makes the warning and error go away, but:

1. I'm not sure that's all one should do, and
2. I'd like to know what to change in the sample source/configuration so that creating the resources from scratch with azd up will create an index using a more up-to-date version.

Any log messages given by the failure

n/a

Expected/desired behavior

No warning or error and the ability to use the index blade UI.

OS and Version?

Linux Mint 21.

azd version?

azd version 1.9.3 (commit e1624330dcc7dde440ecc1eda06aac40e68aa0a3)

Versions

Versions of what?

Mention any other details that might be useful

I looked for 2023-07-01 throughout the source code figuring it had to be specified somewhere, but didn't find it. I assume this is just because things have moved on a bit since the sample was created, but I'm still fairly new to Azure AI stuff and couldn't find what I should update.

When deploying the sample, I didn't use GitHub Codespaces or Remote Containers, I cloned the repo locally, did npm i, and used azd up to create the resources (doing the auth step etc.). The sample runs, but appears to create resources with outdated features.

I've tried dropping all resources, doing npm update throughout, and then creating them again (although I just clone the sample a couple of weeks ago), but azd up failed,¹ so I guess a blanket update wasn't a good idea.

What do I need to change in the sample's code/config to have it create the index with an up-to-date version?

TIA!

---

¹ FWIW, the error was:

4.068 src/plugins/openai.ts(2,34): error TS2307: Cannot find module '@azure/core-http' or its corresponding type declarations.

...building the indexer, but my question isn't about updating the npm packages, it's about resolving the error and warning in the Azure portal.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed.

[tjcrowder]

Ping