You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you correctly pointed out, for migrating from V1 to V2 we have a standalone tool that creates a zip file that can then be used to import schemas into V2.
In latest versions, there's no tool but more a feature in the UI (and, of course, the api) where you have the option to download all the artifacts in a particular installation and also the option to import them (screenshot attached). Those features are also supported in the registry client, in case that helps.
+1 to the info Carles provided. In addition, you can use the REST API if you want to automate the backup of the registry content. The REST API endpoint is here:
You will need an admin level user to perform that REST API call successfully.
As for backing up the topic, that's sadly outside my area of knowledge. I'm not sure what the equivalent of a DB backup is in the Kafka world. But whatever that might be is what you could do. If Mirroring is the equivalent of a DB backup for Kafka, and if you cannot do that, then using the export API is your best bet.
Hi There
Is there a recommendation/guideline for backup/restore of an existing apicurio registry?
I'm thinking about the following:
In our case mirroring the topic is not an option.
Thanks
The text was updated successfully, but these errors were encountered: