azure-search-openai-demo icon indicating copy to clipboard operation
azure-search-openai-demo copied to clipboard

Copy and Backup Index failed and suggestion for migration to production?

Open singloudly90 opened this issue 1 year ago • 3 comments

Please provide us with the following information: What is the suggested process to copy and backup the index? when using https://github.com/Azure-Samples/azure-search-dotnet-utilities/ to backup the index created is not successful

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

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

Minimal steps to reproduce

https://github.com/Azure-Samples/azure-search-dotnet-utilities/ This github is used to copy and backup the index created however it not compatible with this repos index, if create index via azure portal the code will be successful

SAFEGUARD CHECK: Source and target index counts should match Source index contains 1 docs Target index contains 1 docs

Any log messages given by the failure

Error: Search request failed: {"error":{"code":"FeatureNotSupportedInApiVersion","message":"This index was created with a newer version of the Azure Search API and uses features exclusive to that version. Please use the latest API version (2024-03-01-Preview) to manage this index."

Expected/desired behavior

Delete target index test-index in abc search service, if it exists

Create target index test-index-bk in abc search service

Upload index documents from saved JSON files -Uploading documents from file E:\abc\workspace\github\azure-search-dotnet-utilities-main\indexBackup\test-index1.json

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.

singloudly90 avatar Feb 21 '24 07:02 singloudly90

It looks like that repo needs to support the newer API version that we support here. Have you tried filing an issue on that repo?

pamelafox avatar Feb 22 '24 20:02 pamelafox

@pamelafox not yet, because I would like to ask if we has better way of migrate & backup the index to production ?

In same time i will raise issue at there too but it seems not an active repo.

Thank you.

singloudly90 avatar Feb 23 '24 01:02 singloudly90

Good question, I'll CC the search team engineers for their advice: @srbalakr @mattgotteiner We should document the best practice in the productionizing doc.

pamelafox avatar Feb 23 '24 15:02 pamelafox

Thanks @pamelafox for the follow up. Appreciate your help!

singloudly90 avatar Feb 26 '24 03:02 singloudly90