Unable to edit the gptkbindex because of version issues

[en-coded]

Please provide us with the following information:

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

Create a new index gptkbindex.

It seems like the version of gptkbindex that is deployed on the Azure Cognitive Search is not compatible with the available version as per this documentation. I am unable to edit the index till I migrate to the new version.

The chat responses do not work correctly with the new version and I keep getting the following message after the first response. "I'm sorry, but I can't provide the information you're looking for because there are no sources provided."

I see there was a bug fix implemented on chatreadretrieveread.py for index version 2023-07-01. Do we need a bug fix for new version?

azure-search-openai-demo/app/backend/approaches/chatreadretrieveread.py

Line 283 in f696c92

# "2023-07-01-preview" API version has a bug where first response has empty choices

Any log messages given by the failure

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.

Link to the product documentation: https://learn.microsoft.com/en-us/azure/search/vector-search-how-to-create-index?tabs=config-2023-11-01%2Crest-2023-10-01-Preview%2Cpush%2Cportal-check-index

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

[en-coded]

Messages during the migration:

Migrate to vector profile
I acknowledge

I understand the migration process involves creating a new vector profile and assigning it to existing vector fields. Migration is supported to single vector algorithm only.

I understand that once the index is migrated to version 2023-10-01-preview, any index schema update or get operations will no longer support version 2023-07-01-preview. We recommend verifying if there are any scripts or automations outside of portal that are reliant on the 2023-07-01-preview index schema api before completing the migration. Document indexing and querying remain unaffected.

[pamelafox]

Hm, I'm a bit confused. The "2023-07-01-preview" is about the OpenAI version, not the Cognitive Search version. Is your search not finding any results? What does the thought process show in the app? Are you perhaps missing the vector field? Does it work if you turn off vector search adn use only text search?

[zhongshuai-cao]

I just hit the same issue when I check my Azure AI Search (all a sudden all names changed...)

I think the reason is not anything todo with the QnA approaches but the embedding creation. Though I don't need or edit the index for now but I may want it solved. I am concerned if I click migrate button, if it will impact my ability to continue to index more files?

[pamelafox]

Ah interesting, @srbalakr or @mattmsft, can you comment whether it's safe to migrate?

[makalan604]

interested in this as well. as i want to include sourcefile as part of thesoring profile

[mattgotteiner]

I just hit the same issue when I check my Azure AI Search (all a sudden all names changed...)

I think the reason is not anything todo with the QnA approaches but the embedding creation. Though I don't need or edit the index for now but I may want it solved. I am concerned if I click migrate button, if it will impact my ability to continue to index more files?

If you click the migrate button you will still be able to index more files. All it does is create a vector profile - right now the code uses an older version of the SDK that creates a configuration. A profile includes all the functionality of a configuration, along with the newer features.

https://learn.microsoft.com/en-us/azure/search/vector-search-how-to-create-index?tabs=config-2023-11-01%2Crest-2023-11-01%2Cpush%2Cportal-check-index

[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.

[pamelafox]

Thanks for reporting this. The sample has since moved to vector profiles and newer Search APIs. The code now also updates existing indexes to add the needed profiles/vectorizers.

Given the age of this thread and the repo changes, I’m going to close this out. If you still run into issues on the latest main after migrating or recreating your index, please open a new issue with full steps, your index schema/version details, and any logs so I can help troubleshoot.