I generally would recommend exporting data from the old version and then importing into the new one, yes.  Apiman should handle any issues of data compatibility between versions.

This is one of the main reasons the import/export feature was actually written.  The ability to migrate from one version to another, or the ability to migrate from one storage type (RDBMS) to another (Elastic).

-Eric

On Wed, Jan 16, 2019 at 10:05 AM Celso Agra <celso.agra@gmail.com> wrote:

I got it.

Thanks Eric!

So, in this case, would be better to create a new APIMAN instance with a new version

Is there any compatibility among versions in this case?

So, should I export data from old version and import that to the new one?

Best Regards,

Em qua, 16 de jan de 2019 às 12:54, Eric Wittmann <eric.wittmann@redhat.com> escreveu:

I think the typical solution to this is:

1) Export everything via the apiman UI (there is an admin page for this)

2) Shut down

3) Change whatever persistence settings you want to change resulting in a fresh, empty apiman system configured against whatever persistence you want (ES, RDBMS, etc)

4) Start up the new system

5) Import

That *should* work but make sure you back everything up before doing this sort of thing!

-Eric

On Wed, Jan 16, 2019 at 9:06 AM Celso Agra <celso.agra@gmail.com> wrote:

Hi all,

I have a question about elasticsearch and apiman.

So, my apiman instance (v1.3.0) are using embedded elasticsearch, but now, I have to upgrade my instance to an apiman cluster.

so, I've change my apiman.properties, and remove apiman-es.war from deployments. But My question is, how reindex all data from embedded elasticsearch to the new one?

Best regards,

-- 

---
Celso Agra

_______________________________________________
Apiman-user mailing list
Apiman-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user

--

---
Celso Agra