[
https://issues.apache.org/jira/browse/JAMES-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17936186#comment-17936186
]
Jean Helou commented on JAMES-4119:
-----------------------------------
> Maybe we can use webadmin for this wich would make the migration tools
> backend agnostic?
It is actually more complex than one would think to have both backends enabled
in the same app, I proposed instead a one shot self contained migration app
that can connect to both backends and execute the migration. To do this I had
to build a custom guice binding for the JPA stack that doesn´t try to bind to
the generic interfaces.
Doing it in a live app could be done but I don´t think it adds much. I do
intend to make the migration tool a dependency to a fully pg enabled
scaling-pulsar-smtp to have both mains in the docker image and be able to run
the migration from the container.
> Core data migration tool JPA to Postgres
> ----------------------------------------
>
> Key: JAMES-4119
> URL: https://issues.apache.org/jira/browse/JAMES-4119
> Project: James Server
> Issue Type: Improvement
> Components: data
> Reporter: Jean Helou
> Assignee: Jean Helou
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Build a migration tool that allows for an easier migration of all the core
> data from a JPA instance to a Postgres instance for all of the core data
> supported by JPA :
> * Domain list
> * Users
> * Recipient rewrite tables
> * Mail repository Urls
> * Drop lists
> * Sieve quotas and scripts
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
