Hello team, we have developed based on 0.8.44 and added some extension aspects for customization. We are lagging behind a lot of versions, and I have been trying to upgrade recently, but I have encountered quite a few difficulties. Firstly, I will update based on the datahub-upgrade docker. I downloaded datahub upgrade 0.9.6.1 and 0.8.44, and run them with the following errors. 0.9.6.1->

[com.linkedin.metadata.models.registry.ConfigEntityRegistry]: Factory method 'getInstance' threw exception; nested exception is java.lang.IllegalArgumentException: Aspect queryKey does not exist

0.8.44->

[com.linkedin.metadata.models.registry.ConfigEntityRegistry]: Factory method 'getInstance' threw exception; nested exception is java.lang.IllegalArgumentException: Aspect embed does not exist

I found that the biggest change is still the index change. I found that the logic for creating the index has been placed in the upgrade-docker. Previously, I remember that the program also created it when it started. Currently, 1.do I have a way to directly create the latest indexes.? and then re-ingest data. 2.whether datahub-upgrade docker is the only channel to init elasticsearch-index?

Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: 1️⃣ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? 2️⃣ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues?

You might try a restore indices https://datahubproject.io/docs/api/restli/restore-indices/